1. 2001-05-18  [1] [SQL] are NEW and OLD rule attributes broken?         postgresq 
  2. 2001-05-18  [1] [SQL] ON UPDATE CASCADE overhead?                     postgresq 
  3. 2001-05-17  [4] [HACKERS] Re: [SQL] possible row locking bug in 7.0.3 postgresq 
  4. 2001-05-17  [1] Re: [HACKERS] Re: [SQL] possible row locking bug in 7 postgresq 
  5. 2001-04-27  [2] Bug#24832: KMail key bindings interfere with mailed H kde-bugs- 
  6. 2001-04-03  [2] Bug#22828: KDE bug report logs - #22828 duplicate coo kde-bugs- 
  7. 2001-03-28  [2] [SQL] possible row locking bug in 7.0.3 & 7.1         postgresq 
  8. 2001-01-24  [3] [SQL] unreferenced primary keys: garbage collection   postgresq 
  9. 2000-11-13  [1] Re: [SQL] Using a postgres table to maintain unique i postgresq 
 10. 2000-11-09  [1] [SQL] alter table add column implementation undesirab postgresq 
 11. 2000-11-08  [2] [SQL] how to index a numeric(12,2) column?            postgresq 
 12. 2000-10-13  [1] [GENERAL] Is VACUUM ANALYZE a superset of VACUUM?     postgresq 
 13. 2000-09-28  [1] [SQL] transactions surrounding extension functions    postgresq 
 14. 2000-09-26  [1] [SQL] Re: SQL functions not locking properly?         postgresq 
 15. 2000-09-25  [1] [SQL] SQL functions not locking properly?             postgresq 
 16. 2000-09-22  [2] [SQL] C functions and int8?                           postgresq 
 17. 2000-09-20  [1] [GENERAL] 7.0.2 rpm yields broken os.h symlink        postgresq 
 18. 2000-09-19  [2] [GENERAL] Can't connect to 6.5.2 server with 7.0.2 cl postgresq 
 19. 2000-08-17  [5] bug:  libstdc++ container allocator discrepancy       gcc-bugs  
 20. 2000-08-12  [1] [SQL] non-cachable 'C' language functions             postgresq 
 21. 2000-07-08  [1] [SQL] How to get a self-conflicting row level lock?   postgresq