1. 12 Jan, 2001 6 commits
    • Bruce Momjian's avatar
      Update TODO list. · 1c7d7528
      Bruce Momjian authored
      1c7d7528
    • Tom Lane's avatar
      Bring CREATE TABLE syntax synopsis into line with reality; update a · 359459a4
      Tom Lane authored
      bunch of old or poorly-worded documentation.
      359459a4
    • Philip Warner's avatar
      - Check ntuples == 1 for various SELECT statements. · 06ef1ef2
      Philip Warner authored
      - Fix handling of --tables=* (multiple tables never worked properly, AFAICT)
      - strdup() the current user in DB routines
      - Check results of IO routines more carefully.
      - Check results of PQ routines more carefully.
      
      Have not fixed index output yet.
      06ef1ef2
    • Tom Lane's avatar
      Preserve constraints and column defaults during CLUSTER. · 565639cd
      Tom Lane authored
      Wish they were all this easy ...
      565639cd
    • Marc G. Fournier's avatar
      · 1db943b3
      Marc G. Fournier authored
      commit Oleg and Teodor's RD-tree implementation ... this provides the
      regression tests for the GiST changes ... this should be integrated into
      the regular regression tests similar to Vadim's SPI contrib stuff ...
      1db943b3
    • Marc G. Fournier's avatar
      · 0ad7db4b
      Marc G. Fournier authored
      New feature:
         1. Support of variable size keys - new algorithm of insertion to tree
            (GLI - gist layrered insertion). Previous algorithm was implemented
            as described in paper by Joseph M. Hellerstein et.al
            "Generalized Search Trees for Database Systems".  This (old)
            algorithm was not suitable for variable size keys and could be
            not effective ( walking up-down ) in case of multiple levels split
      Bug fixed:
         1. fixed bug in gistPageAddItem - key values were written to disk
            uncompressed. This caused failure if decompression function
            does real job.
         2. NULLs handling - we keep NULLs in tree. Right way is to remove them,
            but we don't know how to inform vacuum about index statistics. This is
            just cosmetic warning message (like in case with R-Tree),
            but I'm not sure how to recognize real problem if we remove NULLs
            and suppress this warning as Tom suggested.
         3. various memory leaks
      
      This work was done by Teodor Sigaev (teodor@stack.net) and
      Oleg Bartunov (oleg@sai.msu.su).
      0ad7db4b
  2. 11 Jan, 2001 7 commits
  3. 10 Jan, 2001 3 commits
  4. 09 Jan, 2001 21 commits
  5. 08 Jan, 2001 3 commits