Skip to content
Snippets Groups Projects
  1. Dec 23, 2006
    • Tom Lane's avatar
      Restructure operator classes to allow improved handling of cross-data-type · a78fcfb5
      Tom Lane authored
      cases.  Operator classes now exist within "operator families".  While most
      families are equivalent to a single class, related classes can be grouped
      into one family to represent the fact that they are semantically compatible.
      Cross-type operators are now naturally adjunct parts of a family, without
      having to wedge them into a particular opclass as we had done originally.
      
      This commit restructures the catalogs and cleans up enough of the fallout so
      that everything still works at least as well as before, but most of the work
      needed to actually improve the planner's behavior will come later.  Also,
      there are not yet CREATE/DROP/ALTER OPERATOR FAMILY commands; the only way
      to create a new family right now is to allow CREATE OPERATOR CLASS to make
      one by default.  I owe some more documentation work, too.  But that can all
      be done in smaller pieces once this infrastructure is in place.
      a78fcfb5
  2. Dec 22, 2006
  3. Dec 21, 2006
  4. Dec 20, 2006
  5. Dec 19, 2006
  6. Dec 18, 2006
  7. Dec 17, 2006
    • Bruce Momjian's avatar
      Fix typo: · cdcee165
      Bruce Momjian authored
      <   While PostgreSQL clients runs fine limited-resource environments, the
      >   While PostgreSQL clients runs fine in limited-resource environments, the
      cdcee165
    • Bruce Momjian's avatar
      Move entry into CLUSTER section: · 6874fb90
      Bruce Momjian authored
      < * Make CLUSTER preserve recently-dead tuples per MVCC requirements
      > 	o Make CLUSTER preserve recently-dead tuples per MVCC requirements
      6874fb90
  8. Dec 16, 2006
  9. Dec 15, 2006
  10. Dec 14, 2006
  11. Dec 13, 2006
  12. Dec 12, 2006
  13. Dec 11, 2006
  14. Dec 10, 2006
Loading