1. 27 Jun, 2006 4 commits
    • Bruce Momjian's avatar
      Will revert in next patch more cleanly. · e99507ea
      Bruce Momjian authored
      > * -Disallow changing DEFAULT expression of a SERIAL column
      e99507ea
    • Bruce Momjian's avatar
      Not done: · 0c99c0fe
      Bruce Momjian authored
      < * -Disallow changing DEFAULT expression of a SERIAL column
      > * %Disallow changing DEFAULT expression of a SERIAL column
      0c99c0fe
    • Bruce Momjian's avatar
      Done: · 62f26936
      Bruce Momjian authored
      < * %Disallow changing DEFAULT expression of a SERIAL column?
      <
      <   This should be done only if the existing SERIAL problems cannot be
      <   fixed.
      <
      > * -Disallow changing DEFAULT expression of a SERIAL column
      62f26936
    • Bruce Momjian's avatar
      Done: · 560feb47
      Bruce Momjian authored
      > 	o -Add PQescapeIdentifier()
      560feb47
  2. 25 Jun, 2006 2 commits
    • Bruce Momjian's avatar
      Update my info: · bc28f58b
      Bruce Momjian authored
      > * Bruce is Bruce Momjian <bruce@momjian.us> of EnterpriseDB
      bc28f58b
    • Bruce Momjian's avatar
      Add: · f5940e7b
      Bruce Momjian authored
      < * Reuse index tuples that point to rows that are not visible to anyone?
      > * Reuse index tuples that point to heap tuples that are not visible to
      >   anyone?
      f5940e7b
  3. 24 Jun, 2006 2 commits
    • Bruce Momjian's avatar
      Update entry: · ac7a126d
      Bruce Momjian authored
      < * Allow heap reuse of UPDATEd rows if old and new versions are on the
      <   same heap page?
      > * Allow heap reuse of UPDATEd rows if no indexed columns are changed,
      >   and old and new versions are on the same heap page?
      <   This is possible for same-page updates because a single index row
      <   can point to both old and new values.
      >   While vacuum handles DELETEs fine, updating of non-indexed columns, like
      >   counters, are difficult for VACUUM to handle efficiently.  This method
      >   is possible for same-page updates because a single index row can be
      >   used to point to both old and new values.
      ac7a126d
    • Bruce Momjian's avatar
      Add UPDATE entry for row reuse. · fc6a2293
      Bruce Momjian authored
      >
      > * Allow heap reuse of UPDATEd rows if old and new versions are on the
      >   same heap page?
      >
      >   This is possible for same-page updates because a single index row
      >   can point to both old and new values.
      >   http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php
      fc6a2293
  4. 18 Jun, 2006 1 commit
  5. 16 Jun, 2006 14 commits
  6. 15 Jun, 2006 5 commits
  7. 14 Jun, 2006 12 commits