1. 12 Mar, 2002 1 commit
    • Tom Lane's avatar
      Restructure representation of join alias variables. An explicit JOIN · 6eeb95f0
      Tom Lane authored
      now has an RTE of its own, and references to its outputs now are Vars
      referencing the JOIN RTE, rather than CASE-expressions.  This allows
      reverse-listing in ruleutils.c to use the correct alias easily, rather
      than painfully reverse-engineering the alias namespace as it used to do.
      Also, nested FULL JOINs work correctly, because the result of the inner
      joins are simple Vars that the planner can cope with.  This fixes a bug
      reported a couple times now, notably by Tatsuo on 18-Nov-01.  The alias
      Vars are expanded into COALESCE expressions where needed at the very end
      of planning, rather than during parsing.
      Also, beginnings of support for showing plan qualifier expressions in
      EXPLAIN.  There are probably still cases that need work.
      initdb forced due to change of stored-rule representation.
      6eeb95f0
  2. 11 Mar, 2002 10 commits
  3. 10 Mar, 2002 4 commits
  4. 09 Mar, 2002 5 commits
  5. 08 Mar, 2002 12 commits
  6. 07 Mar, 2002 5 commits
  7. 06 Mar, 2002 3 commits
    • Bruce Momjian's avatar
      Fix syntax error introduced by patch. · 9178b7fc
      Bruce Momjian authored
      9178b7fc
    • Bruce Momjian's avatar
      I've attached a patch which implements Bob Jenkin's hash function for · 7ab74673
      Bruce Momjian authored
      PostgreSQL. This hash function replaces the one used by hash indexes and
      the catalog cache. Hash joins use a different, relatively poor-quality
      hash function, but I'll fix that later.
      
      As suggested by Tom Lane, this patch also changes the size of the fixed
      hash table used by the catalog cache to be a power-of-2 (instead of a
      prime: I chose 256 instead of 257). This allows the catcache to lookup
      hash buckets using a simple bitmask. This should improve the performance
      of the catalog cache slightly, since the previous method (modulo a
      prime) was slow.
      
      In my tests, this improves the performance of hash indexes by between 4%
      and 8%; the performance when using btree indexes or seqscans is
      basically unchanged.
      
      Neil Conway <neilconway@rogers.com>
      7ab74673
    • Bruce Momjian's avatar
      Enable ALTER TABLE ADD PRIMARY KEY for pg_dump, for performance reasons · 5b5cef9a
      Bruce Momjian authored
      so index is not on table during COPY.
      
      > > AFAICT, the patch I posted to -patches a little while to enable the
      > > usage of ALTER TABLE ADD PRIMARY KEY by pg_dump hasn't been applied, nor
      > > is it in the unapplied patches list. I was under the impression that
      > > this was in the queue for application -- did it just get lost?
      
      Neil Conway <neilconway@rogers.com>
      5b5cef9a