1. 20 Oct, 2007 3 commits
  2. 19 Oct, 2007 3 commits
  3. 18 Oct, 2007 7 commits
  4. 17 Oct, 2007 3 commits
  5. 16 Oct, 2007 11 commits
  6. 15 Oct, 2007 4 commits
  7. 14 Oct, 2007 1 commit
  8. 13 Oct, 2007 8 commits
    • Tom Lane's avatar
      Ooops, forgot about adding -DFRONTEND. · cd8e1f50
      Tom Lane authored
      cd8e1f50
    • Tom Lane's avatar
      Migrate the former contrib/txid module into core. This will make it easier · 18e3fcc3
      Tom Lane authored
      for Slony and Skytools to depend on it.  Per discussion.
      18e3fcc3
    • Tom Lane's avatar
    • Tom Lane's avatar
      041a8b37
    • Tom Lane's avatar
      Strengthen type_sanity's check on pg_type.typarray. It failed to · 2ffc0e88
      Tom Lane authored
      complain about types that didn't have typarray set.  Noted while
      working on txid patch.
      2ffc0e88
    • Tom Lane's avatar
      Guard against possible double free during error escape from XML · ff1de5ce
      Tom Lane authored
      functions.  Patch for the reported issue from Kris Jurka, some
      other potential trouble spots plugged by Tom.
      ff1de5ce
    • Tom Lane's avatar
      Fix the inadvertent libpq ABI breakage discovered by Martin Pitt: the · 8468146b
      Tom Lane authored
      renumbering of encoding IDs done between 8.2 and 8.3 turns out to break 8.2
      initdb and psql if they are run with an 8.3beta1 libpq.so.  For the moment
      we can rearrange the order of enum pg_enc to keep the same number for
      everything except PG_JOHAB, which isn't a problem since there are no direct
      references to it in the 8.2 programs anyway.  (This does force initdb
      unfortunately.)
      
      Going forward, we want to fix things so that encoding IDs can be changed
      without an ABI break, and this commit includes the changes needed to allow
      libpq's encoding IDs to be treated as fully independent of the backend's.
      The main issue is that libpq clients should not include pg_wchar.h or
      otherwise assume they know the specific values of libpq's encoding IDs,
      since they might encounter version skew between pg_wchar.h and the libpq.so
      they are using.  To fix, have libpq officially export functions needed for
      encoding name<=>ID conversion and validity checking; it was doing this
      anyway unofficially.
      
      It's still the case that we can't renumber backend encoding IDs until the
      next bump in libpq's major version number, since doing so will break the
      8.2-era client programs.  However the code is now prepared to avoid this
      type of problem in future.
      
      Note that initdb is no longer a libpq client: we just pull in the two
      source files we need directly.  The patch also fixes a few places that
      were being sloppy about checking for an unrecognized encoding name.
      8468146b
    • Tom Lane's avatar
      Fix ALTER COLUMN TYPE to preserve the tablespace and reloptions of indexes · 537e92e4
      Tom Lane authored
      it affects.  The original coding neglected tablespace entirely (causing
      the indexes to move to the database's default tablespace) and for an index
      belonging to a UNIQUE or PRIMARY KEY constraint, it would actually try to
      assign the parent table's reloptions to the index :-(.  Per bug #3672 and
      subsequent investigation.
      
      8.0 and 8.1 did not have reloptions, but the tablespace bug is present.
      537e92e4