Skip to content
Snippets Groups Projects
  1. Apr 12, 2008
    • Tom Lane's avatar
      Fix several datatype input functions that were allowing unused bytes in their · c846f7ca
      Tom Lane authored
      results to contain uninitialized, unpredictable values.  While this was okay
      as far as the datatypes themselves were concerned, it's a problem for the
      parser because occurrences of the "same" literal might not be recognized as
      equal by datumIsEqual (and hence not by equal()).  It seems sufficient to fix
      this in the input functions since the only critical use of equal() is in the
      parser's comparisons of ORDER BY and DISTINCT expressions.
      Per a trouble report from Marc Cousin.
      
      Patch all the way back.  Interestingly, array_in did not have the bug before
      8.2, which may explain why the issue went unnoticed for so long.
      c846f7ca
  2. Apr 11, 2008
    • Bruce Momjian's avatar
      Update wording: · 00b1827a
      Bruce Momjian authored
      < * Allow functions to control the transaction state
      > * Allow calling of a procedure outside a SELECT that can control the
      >   transaction state
      00b1827a
    • Bruce Momjian's avatar
      Changed TODO wording: · accbddc9
      Bruce Momjian authored
      < * Support procedures, which return no value
      > * Allow functions to control the transaction state
      accbddc9
    • Bruce Momjian's avatar
      Add TODO: · 94255057
      Bruce Momjian authored
      > * Support procedures, which return no value
      >
      >   http://archives.postgresql.org/pgsql-hackers/2007-10/msg01375.php
      94255057
    • Bruce Momjian's avatar
      Update URLs for dead space map. · a464dc07
      Bruce Momjian authored
      a464dc07
    • Bruce Momjian's avatar
      Fix main README typo. · 3fa352da
      Bruce Momjian authored
      Brendan Jurd
      3fa352da
    • Tom Lane's avatar
      Replace "amgetmulti" AM functions with "amgetbitmap", in which the whole · 4e82a954
      Tom Lane authored
      indexscan always occurs in one call, and the results are returned in a
      TIDBitmap instead of a limited-size array of TIDs.  This should improve
      speed a little by reducing AM entry/exit overhead, and it is necessary
      infrastructure if we are ever to support bitmap indexes.
      
      In an only slightly related change, add support for TIDBitmaps to preserve
      (somewhat lossily) the knowledge that particular TIDs reported by an index
      need to have their quals rechecked when the heap is visited.  This facility
      is not really used yet; we'll need to extend the forced-recheck feature to
      plain indexscans before it's useful, and that hasn't been coded yet.
      The intent is to use it to clean up 8.3's horrid @@@ kluge for text search
      with weighted queries.  There might be other uses in future, but that one
      alone is sufficient reason.
      
      Heikki Linnakangas, with some adjustments by me.
      4e82a954
  3. Apr 10, 2008
  4. Apr 09, 2008
  5. Apr 08, 2008
  6. Apr 07, 2008
  7. Apr 06, 2008
    • Tom Lane's avatar
      Improve hash_any() to use word-wide fetches when hashing suitably aligned · 26043592
      Tom Lane authored
      data.  This makes for a significant speedup at the cost that the results
      now vary between little-endian and big-endian machines; which forces us
      to add explicit ORDER BYs in a couple of regression tests to preserve
      machine-independent comparison results.  Also, force initdb by bumping
      catversion, since the contents of hash indexes will change (at least on
      big-endian machines).
      
      Kenneth Marshall and Tom Lane, based on work from Bob Jenkins.  This commit
      does not adopt Bob's new faster mix() algorithm, however, since we still need
      to convince ourselves that that doesn't degrade the quality of the hashing.
      26043592
  8. Apr 05, 2008
  9. Apr 04, 2008
Loading