• Text Size: Normal / Large
• Donate
• Contact

Section Navigation

• Community
• Contributors
• Mailing Lists
  • Subscribe
  • User lists
  • Developer lists
    • pgsql-committers
    • pgsql-hackers
    • pgsql-patches
    • pgsql-www
  • Regional lists
  • Project lists
  • User groups
  • Inactive lists
• IRC
• Featured Users
• International Sites
• Propaganda
• Resources
• Weekly News
• Community login
  • Profile
  • Lost password

pgsql-hackers 2006-05 Chronological Index (3/8)

• Thread Index
• [Prev Page]
• [Next Page]

• 24 May 2006
  • Re: Compression and on-disk sorting Jim C. Nasby
  • Re: error-free disabling of individual child partition Simon Riggs
  • Re: Improving ALTER TYPE support Tom Lane
  • Re: file-locking and postmaster.pid Alvaro Herrera
  • Re: file-locking and postmaster.pid korry
  • Re: file-locking and postmaster.pid korry
  • Re: file-locking and postmaster.pid Andreas Joseph Krogh
  • Re: file-locking and postmaster.pid Andreas Joseph Krogh
  • Re: Further reduction of bufmgr lock contention Tom Lane
  • Re: Why is CVS server so slow? Magnus Hagander
  • Re: Why is CVS server so slow? Dave Page
  • Re: problem with PQsendQuery/PQgetResult and COPY FROM statement Tom Lane
  • Re: Why is CVS server so slow? Marc G. Fournier
  • Re: Improving ALTER TYPE support John Jawed
  • Re: Further reduction of bufmgr lock contention Josh Berkus
  • Re: file-locking and postmaster.pid Andrej Ricnik-Bay
  • Re: Updatable views/with check option parsing Tom Lane
  • Re: error-free disabling of individual child partition Tom Lane
  • Re: error-free disabling of individual child partition Andrew Dunstan
  • Re: error-free disabling of individual child partition Alvaro Herrera
  • Re: error-free disabling of individual child partition Hannu Krosing
  • Re: Updatable views/with check option parsing Andrew Dunstan
  • Re: Improving ALTER TYPE support Tom Lane
  • Re: error-free disabling of individual child partition Tom Lane
  • Re: error-free disabling of individual child partition Simon Riggs
  • Re: Updatable views/with check option parsing Hannu Krosing
  • Updatable views/with check option parsing Peter Eisentraut
  • Re: file-locking and postmaster.pid Andreas Joseph Krogh
  • Re: file-locking and postmaster.pid Andreas Joseph Krogh
  • compiling source code!!!!!!!!!!!!!!!!!!!!!!!!!!!!! sibel karaasma
  • Re: LIKE, leading percent, bind parameters and indexes Zeugswetter Andreas DCP SD
  • Re: error-free disabling of individual child partition Hannu Krosing
  • Re: Further reduction of bufmgr lock contention Gavin Hamill
  • Re: error-free disabling of individual child partition Hannu Krosing
  • Re: error-free disabling of individual child partition Zeugswetter Andreas DCP SD
  • Re: LIKE, leading percent, bind parameters and indexes Qingqing Zhou
  • Re: Performance Issues Tom Lane
  • Re: Performance Issues Christopher Kings-Lynne
  • Re: Performance Issues Dhanaraj M
  • Re: Improving ALTER TYPE support John Jawed
  • Re: Why is CVS server so slow? Tom Lane
  • Re: LIKE, leading percent, bind parameters and indexes Tom Lane
  • Re: problem with PQsendQuery/PQgetResult and COPY FROM statement max . poletto
  • Re: Why is CVS server so slow? Josh Berkus
  • Re: Improving ALTER TYPE support Josh Berkus
  • Improving ALTER TYPE support John Jawed
• 23 May 2006
  • Re: Why is CVS server so slow? Michael Fuhr
  • Re: SQL compliant interval implementation Michael Glaesemann
  • Re: Porting MSSQL to PGSQL -- triggers Mischa Sandberg
  • Re: Why is CVS server so slow? Marc G. Fournier
  • Re: SQL compliant interval implementation Josh Berkus
  • LIKE, leading percent, bind parameters and indexes Rodrigo Hjort
  • Re: SQL compliant interval implementation Bruce Momjian
  • Re: SQL compliant interval implementation Brendan Jurd
  • Re: SQL compliant interval implementation Josh Berkus
  • Re: SQL compliant interval implementation Tom Lane
  • Re: SQL compliant interval implementation Bruce Momjian
  • SQL compliant interval implementation Brendan Jurd
  • Re: error-free disabling of individual child partition Bruce Momjian
  • Re: API changes in patch release Andrew Dunstan
  • Re: API changes in patch release Magnus Hagander
  • Re: [GENERAL] Weird ..... (a=1 or a=2) <> (a=2 or a=1) Tom Lane
  • Re: API changes in patch release Bruce Momjian
  • Re: Update on sort-compression stuff Simon Riggs
  • Re: [GENERAL] Weird ..... (a=1 or a=2) <> (a=2 or a=1) Merlin Moncure
  • Re: Update on sort-compression stuff Tom Lane
  • Re: [GENERAL] autovacuum "connections" are hidden Jim C. Nasby
  • Re: file-locking and postmaster.pid Adis Nezirovic
  • Re: error-free disabling of individual child partition Simon Riggs
  • Re: file-locking and postmaster.pid Tom Lane
  • Re: error-free disabling of individual child partition Tom Lane
  • Re: file-locking and postmaster.pid Adis Nezirovic
  • Re: Performance Issues Mark Woodward
  • Re: error-free disabling of individual child partition Simon Riggs
  • Re: file-locking and postmaster.pid Tom Lane
  • Re: New feature proposal Marc Munro
  • Re: file-locking and postmaster.pid Andreas Joseph Krogh
  • Re: Further reduction of bufmgr lock contention Tom Lane
  • Re: file-locking and postmaster.pid Tom Lane
  • Re: Further reduction of bufmgr lock contention Gavin Hamill
  • Re: error-free disabling of individual child partition Tom Lane
  • Re: error-free disabling of individual child partition Simon Riggs
  • Re: [ADMIN] does wal archiving block the current client Tom Lane
  • Re: error-free disabling of individual child partition Hannu Krosing
  • file-locking and postmaster.pid Andreas Joseph Krogh
  • Why is CVS server so slow? Simon Riggs
  • Re: [ADMIN] does wal archiving block the current client Simon Riggs
  • Re: [ADMIN] does wal archiving block the current client connection? Tom Lane
  • Re: [ADMIN] does wal archiving block the current client Simon Riggs
  • Re: error-free disabling of individual child partition Simon Riggs
  • Re: [ADMIN] does wal archiving block the current client connection? Tom Lane
  • Re: [ADMIN] does wal archiving block the current client Simon Riggs
  • Re: Performance Issues Dave Cramer
  • Re: error-free disabling of individual child partition Csaba Nagy
  • Re: error-free disabling of individual child partition Simon Riggs
  • Re: Performance Issues Richard Huxton
  • Re: error-free disabling of individual child partition Tom Lane
  • Re: error-free disabling of individual child partition Hannu Krosing
  • Re: error-free disabling of individual child partition Tom Lane
  • Re: Performance Issues Douglas McNaught
  • Performance Issues Dhanaraj M
  • Re: error-free disabling of individual child partition Hannu Krosing
  • Re: error-free disabling of individual child partition Simon Riggs
  • Re: error-free disabling of individual child partition Zeugswetter Andreas DCP SD
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Thomas Hallgren
  • API changes in patch release Thomas Hallgren
  • Re: [ADMIN] does wal archiving block the current client connection? Jeff Frost
  • Re: [ADMIN] does wal archiving block the current client connection? Tom Lane
  • Re: [ADMIN] does wal archiving block the current client connection? Jeff Frost
• 22 May 2006
  • Re: group by points Bruno Wolff III
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Tom Lane
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but Andrew Dunstan
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Tom Lane
  • Re: group by points Tom Lane
  • Re: pgbench create index anomoly Tom Lane
  • Re: FW: iDefense Q2 2006 Vulnerability Challenge Robert Treat
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but Mischa Sandberg
  • Re: [GENERAL] autovacuum "connections" are hidden Casey Duncan
  • Re: Porting MSSQL to PGSQL: trace and profile Mischa Sandberg
  • Re: [GENERAL] autovacuum "connections" are hidden Alvaro Herrera
  • Re: Compiling PL/Perl and Pl/Python on x86_64 Theo Schlossnagle
  • Re: error-free disabling of individual child partition Andrew Dunstan
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS Bruce Momjian
  • Re: error-free disabling of individual child partition Simon Riggs
  • Re: Compiling PL/Perl and Pl/Python on x86_64 Andrew Dunstan
  • Re: error-free disabling of individual child partition Andrew Dunstan
  • Re: group by points Bruno Wolff III
  • Re: pgbench create index anomoly Jim C. Nasby
  • Re: pgbench create index anomoly Simon Riggs
  • Re: Update on sort-compression stuff Tom Lane
  • Re: Update on sort-compression stuff Jim C. Nasby
  • Re: error-free disabling of individual child partition Jim C. Nasby
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Jim C. Nasby
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS Jim C. Nasby
  • Re: error-free disabling of individual child partition Andrew Dunstan
  • Update on sort-compression stuff Martijn van Oosterhout
  • Re: error-free disabling of individual child partition tables Jim C. Nasby
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Jim C. Nasby
  • Re: [pgsql-advocacy] [OT] MySQL is bad, but THIS bad? Martijn van Oosterhout
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Alvaro Herrera
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS Bruce Momjian
  • pgbench create index anomoly Jim C. Nasby
  • Re: [pgsql-advocacy] [OT] MySQL is bad, but THIS bad? Dawid Kuroczko
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Martijn van Oosterhout
  • Re: [pgsql-advocacy] [OT] MySQL is bad, but THIS bad? Mark Woodward
  • error-free disabling of individual child partition tables April Lorenzen
  • Re: [pgsql-advocacy] [OT] MySQL is bad, but THIS bad? Jim C. Nasby
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Jim C. Nasby
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Harald Fuchs
  • Re: Compiling PL/Perl and Pl/Python on x86_64 imacat
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Dawid Kuroczko
  • Re: Duplicate definition of LOCALEDIR Tom Lane
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Martijn van Oosterhout
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Jim C. Nasby
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Jim C. Nasby
  • Re: SSL certificate info on SQL level and HSM support for libpq Tom Lane
  • Re: Duplicate definition of LOCALEDIR Martijn van Oosterhout
  • Re: [OT] MySQL is bad, but THIS bad? Hannu Krosing
  • Re: String Similarity Mark Woodward
  • Duplicate definition of LOCALEDIR Peter Eisentraut
  • Re: group by points Albe Laurenz
  • Re: SSL certificate info on SQL level and HSM support for libpq Martijn van Oosterhout
  • Re: SSL certificate info on SQL level and HSM support for libpq Victor B. Wagner
  • Re: problem with PQsendQuery/PQgetResult and COPY FROM statement Martijn van Oosterhout
  • Re: String Similarity Christopher Kings-Lynne
• 21 May 2006
  • Re: FW: iDefense Q2 2006 Vulnerability Challenge Tom Lane
  • Re: problem with PQsendQuery/PQgetResult and COPY FROM statement Tom Lane
  • Re: Porting MSSQL to PGSQL (Was: [OT] MySQL is bad, but THIS bad?) Josh Berkus
  • Re: problem with PQsendQuery/PQgetResult and COPY FROM statement Volkan YAZICI
  • Re: [ADMIN] does wal archiving block the current client connection? Jeff Frost
  • Re: [ADMIN] does wal archiving block the current client connection? Simon Riggs
  • Re: [ADMIN] does wal archiving block the current client connection? Jeff Frost
  • FW: iDefense Q2 2006 Vulnerability Challenge Magnus Hagander
  • Re: COMMIT leads to ROLLBACK Jaime Casanova
  • Re: COMMIT leads to ROLLBACK Gurjeet Singh
  • Re: COMMIT leads to ROLLBACK Gurjeet Singh
  • Re: COMMIT leads to ROLLBACK Jaime Casanova
  • Re: COMMIT leads to ROLLBACK Tom Lane
  • COMMIT leads to ROLLBACK Gurjeet Singh
  • Re: Compression and on-disk sorting Martijn van Oosterhout

• Thread Index
• [Prev Page]
• [Next Page]