1. 23 3月, 2002 1 次提交
  2. 21 1月, 2002 1 次提交
  3. 08 12月, 2001 1 次提交
  4. 14 9月, 2001 1 次提交
  5. 03 9月, 2001 1 次提交
  6. 22 8月, 2001 1 次提交
    • T
      Restructure pg_opclass, pg_amop, and pg_amproc per previous discussions in · f933766b
      Tom Lane 提交于
      pgsql-hackers.  pg_opclass now has a row for each opclass supported by each
      index AM, not a row for each opclass name.  This allows pg_opclass to show
      directly whether an AM supports an opclass, and furthermore makes it possible
      to store additional information about an opclass that might be AM-dependent.
      pg_opclass and pg_amop now store "lossy" and "haskeytype" information that we
      previously expected the user to remember to provide in CREATE INDEX commands.
      Lossiness is no longer an index-level property, but is associated with the
      use of a particular operator in a particular index opclass.
      
      Along the way, IndexSupportInitialize now uses the syscaches to retrieve
      pg_amop and pg_amproc entries.  I find this reduces backend launch time by
      about ten percent, at the cost of a couple more special cases in catcache.c's
      IndexScanOK.
      
      Initial work by Oleg Bartunov and Teodor Sigaev, further hacking by Tom Lane.
      
      initdb forced.
      f933766b
  7. 07 8月, 2001 1 次提交
  8. 16 7月, 2001 1 次提交
  9. 18 5月, 2001 1 次提交
  10. 14 1月, 2001 1 次提交
  11. 26 12月, 2000 1 次提交
  12. 06 10月, 2000 1 次提交
  13. 13 9月, 2000 1 次提交
  14. 19 6月, 2000 1 次提交
  15. 03 5月, 2000 1 次提交
  16. 23 4月, 2000 1 次提交
  17. 11 4月, 2000 1 次提交
  18. 16 3月, 2000 1 次提交
  19. 22 7月, 1999 1 次提交
  20. 07 7月, 1999 1 次提交
  21. 29 12月, 1998 1 次提交
  22. 31 10月, 1998 1 次提交
  23. 15 10月, 1998 1 次提交
  24. 22 9月, 1998 1 次提交
  25. 16 9月, 1998 1 次提交
  26. 07 9月, 1998 1 次提交
  27. 13 5月, 1998 1 次提交