• 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 2005-12 Chronological Index (3/8)

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

• 21 December 2005
  • Re: localization problem (and solution) Tom Lane
  • Windows Installer Bug (Probably) Ilias Goudaropoulos
  • problem with nasty latin2 sorting Anna Domachowska
  • Re: status of concurrent VACUUM patch ... Hannu Krosing
  • Re: localization problem (and solution) Andreas Seltenreich
  • I am back online again Bruce Momjian
• 20 December 2005
  • Re: localization problem (and solution) Tom Lane
  • Re: status of concurrent VACUUM patch ... Tom Lane
  • status of concurrent VACUUM patch ... Hans-Jürgen Schönig
  • Re: Automatic function replanning Rick Gigger
  • Re: Disparity in search_path SHOW and SET Tom Lane
  • Re: Disparity in search_path SHOW and SET Greg Sabino Mullane
  • Re: Disparity in search_path SHOW and SET Tom Lane
  • Disparity in search_path SHOW and SET Greg Sabino Mullane
  • Re: [pgadmin-hackers] Client-side password encryption Dave Page
  • Re: localization problem (and solution) Manuel Sugawara
  • Re: Lock issue when trying to vacuum db Jess Balint
  • Re: lo function changed in PostgreSQL 8.1.1 Premsun Choltanwanich
  • Re: localization problem (and solution) Tom Lane
  • localization problem (and solution) Manuel Sugawara
  • Re: Lock issue when trying to vacuum db Tom Lane
  • Re: [pgadmin-hackers] Client-side password encryption Christopher Kings-Lynne
  • Re: [pgadmin-hackers] Client-side password encryption Alvaro Herrera
  • Re: [pgadmin-hackers] Client-side password encryption Christopher Kings-Lynne
• 19 December 2005
  • Re: Trouble building 8.1.1 on Tru64 UNIX 5.1 Albert Chin
  • Re: Trouble building 8.1.1 on Tru64 UNIX 5.1 Tom Lane
  • Lock issue when trying to vacuum db Jess Balint
  • Re: Trouble building 8.1.1 on Tru64 UNIX 5.1 Albert Chin
  • Re: Trouble building 8.1.1 on Tru64 UNIX 5.1 Tom Lane
  • free Sun T2000 for PostgreSQL community? Michael Adler
  • Re: [pgadmin-hackers] Client-side password encryption Andreas Pflug
  • Trouble building 8.1.1 on Tru64 UNIX 5.1 Albert Chin
  • Re: Automatic function replanning Jim C. Nasby
  • Re: [pgadmin-hackers] Client-side password encryption Andrew Dunstan
  • Re: Re: Which qsort is used Luke Lonergan
  • Re: [pgadmin-hackers] Client-side password encryption Dave Page
  • Re: [pgadmin-hackers] Client-side password encryption Tom Lane
  • Re: [pgadmin-hackers] Client-side password encryption Dave Page
  • Re: [pgadmin-hackers] Client-side password encryption Magnus Hagander
  • Re: [pgadmin-hackers] Client-side password encryption Dave Page
  • Re: [pgadmin-hackers] Client-side password encryption Andreas Pflug
  • Re: [pgadmin-hackers] Client-side password encryption Martijn van Oosterhout
  • Re: [pgadmin-hackers] Client-side password encryption Magnus Hagander
  • Re: Re: Which qsort is used Martijn van Oosterhout
  • Re: [pgadmin-hackers] Client-side password encryption Dave Page
  • Re: [pgadmin-hackers] Client-side password encryption Martijn van Oosterhout
  • Re: [pgadmin-hackers] Client-side password encryption Dave Page
  • Re: [pgadmin-hackers] Client-side password encryption Martijn van Oosterhout
  • Re: [pgadmin-hackers] Client-side password encryption Dave Page
  • Re: [pgadmin-hackers] Client-side password encryption Martijn van Oosterhout
  • Re: [pgadmin-hackers] Client-side password encryption Dave Page
  • Re: Recovery from multi trouble OKADA Satoshi
  • Re: [pgadmin-hackers] Client-side password encryption Tom Lane
  • Re: Recovery from multi trouble Tom Lane
  • Re: [pgadmin-hackers] Client-side password encryption Christopher Kings-Lynne
  • Recovery from multi trouble OKADA Satoshi
  • Re: Automatic function replanning Trent Shipley
  • Re: [pgadmin-hackers] Client-side password encryption Peter Eisentraut
• 18 December 2005
  • Re: Log of CREATE USER statement Andreas Pflug
  • Re: Automatic function replanning Bruce Momjian
  • Re: Automatic function replanning Christopher Browne
  • Re: Automatic function replanning Christopher Browne
  • Re: Automatic function replanning Tom Lane
  • Re: Log of CREATE USER statement Peter Eisentraut
  • Re: Automatic function replanning Bruce Momjian
  • Re: Automatic function replanning Chris Browne
• 17 December 2005
  • Re: Automatic function replanning Lukas Smith
  • Re: number of loaded/unloaded COPY rows Tom Lane
  • Re: number of loaded/unloaded COPY rows Bruce Momjian
  • Re: number of loaded/unloaded COPY rows Bruce Momjian
  • Re: Automatic function replanning Bruce Momjian
  • Re: Automatic function replanning Jim C. Nasby
  • Re: psql and COPY BINARY Bruce Momjian
  • Re: number of loaded/unloaded COPY rows Volkan YAZICI
  • Re: Immodest Proposal: pg_catalog.pg_ddl Bruce Momjian
  • Re: Re: Which qsort is used Dann Corbit
  • Re: Re: Which qsort is used Tom Lane
  • Re: Re: Which qsort is used Dann Corbit
  • Re: Re: Which qsort is used Qingqing Zhou
  • Re: Re: Which qsort is used Dann Corbit
  • Re: Re: Which qsort is used Tom Lane
  • Re: Automatic function replanning Bruce Momjian
  • Re: Which qsort is used Mark Kirkwood
  • Re: number of loaded/unloaded COPY rows Bruce Momjian
  • Re: Re: Which qsort is used Dann Corbit
  • Re: Re: Which qsort is used Qingqing Zhou
  • Re: Re: Which qsort is used Bruce Momjian
• 16 December 2005
  • Re: reducing bloat in pg_statistic Tom Lane
  • Re: second "begin transaction" emits a warning Robert Treat
  • Re: second "begin transaction" emits a warning Tom Lane
  • reducing bloat in pg_statistic Robert Treat
  • second "begin transaction" emits a warning Jaime Casanova
  • Re: Self-modifying code Alvaro Herrera
  • Re: Web archive issue? Jim C. Nasby
  • Re: Improving planning of outer joins Tom Lane
  • Re: Improving planning of outer joins Alvaro Herrera
  • Re: Improving planning of outer joins Tom Lane
  • Re: Improving planning of outer joins Alvaro Herrera
  • Re: Web archive issue? Martijn van Oosterhout
  • Re: Improving planning of outer joins Simon Riggs
  • Re: Improving planning of outer joins Simon Riggs
  • Re: Web archive issue? Marc G. Fournier
  • Web archive issue? Martijn van Oosterhout
  • I am back online Bruce Momjian
  • Re: Which qsort is used Jeff Trout
  • Re: Which qsort is used Dann Corbit
  • Re: Which qsort is used Qingqing Zhou
  • Re: Which qsort is used Luke Lonergan
  • Re: Which qsort is used Qingqing Zhou
  • Re: Which qsort is used Tom Lane
  • Re: Improving planning of outer joins Christopher Kings-Lynne
  • Re: Improving planning of outer joins Christopher Kings-Lynne
  • Re: Which qsort is used Dann Corbit
• 15 December 2005
  • Re: Which qsort is used Qingqing Zhou
  • Re: Which qsort is used Tom Lane
  • Re: Which qsort is used Greg Stark
  • Re: Interesting speed anomaly Zoltan Boszormenyi
  • Re: postgres version control? Jim C. Nasby
  • postgres version control? Amit Kulkarni
  • Re: 7.3 failure on platypus Jim C. Nasby
  • Re: 7.3 failure on platypus Tom Lane
  • Re: 7.3 failure on platypus Andrew Dunstan
  • Re: 7.3 failure on platypus Robert Treat
  • Re: Which qsort is used Qingqing Zhou
  • Re: Automatic function replanning Jim C. Nasby
  • Re: Which qsort is used Jim C. Nasby
  • Re: 7.3 failure on platypus Jim C. Nasby
  • Re: Improving planning of outer joins Jim C. Nasby
  • Re: Interesting speed anomaly Jim C. Nasby
  • Re: Improving planning of outer joins Tom Lane
  • Re: Improving planning of outer joins Greg Stark
  • Re: 7.3 failure on platypus Mark Kirkwood
  • Re: ANSI SQL, CASE expression Conformance F262, F263 any info Pavel Stehule
  • Re: 7.3 failure on platypus Mark Kirkwood
  • Re: Extended queries Tom Lane
  • Re: Extended queries Tatsuo Ishii
  • Re: 7.3 failure on platypus Tom Lane
  • Re: Extended queries Tom Lane
  • Re: Self-modifying code Tom Lane
  • Re: Which qsort is used Qingqing Zhou
  • Self-modifying code Alvaro Herrera
  • Re: Which qsort is used Luke Lonergan
  • Re: lo function changed in PostgreSQL 8.1.1 Premsun Choltanwanich
  • Improving planning of outer joins Tom Lane
  • Re: Refactoring psql for backward-compatibility Christopher Kings-Lynne
  • Re: Refactoring psql for backward-compatibility David Fetter
  • Re: Immodest Proposal: pg_catalog.pg_ddl Christopher Kings-Lynne
  • Re: Immodest Proposal: pg_catalog.pg_ddl Christopher Kings-Lynne
  • Re: psql and COPY BINARY Christopher Kings-Lynne
  • Re: psql and COPY BINARY Christopher Kings-Lynne
  • Re: Refactoring psql for backward-compatibility Christopher Kings-Lynne
  • Extended queries Tatsuo Ishii
• 14 December 2005
  • Re: Refactoring psql for backward-compatibility Hannu Krosing
  • Re: 7.3 failure on platypus Mark Kirkwood
  • Re: Interesting speed anomaly Zoltan Boszormenyi
  • Re: Interesting speed anomaly Gavin Sherry
  • Re: Interesting speed anomaly Gavin Sherry
  • Re: [Bulk] Re: [Bug] Server Crash, possible security exploit, Francisco Figueiredo Jr.
  • Re: Interesting speed anomaly Zoltan Boszormenyi
  • Re: psql and COPY BINARY Andreas Pflug
  • Re: Immodest Proposal: pg_catalog.pg_ddl Andreas Pflug
  • Re: psql and COPY BINARY Tom Lane
  • Re: psql and COPY BINARY Andreas Pflug
  • Re: Cost-based optimizers Christopher Browne
  • Re: Immodest Proposal: pg_catalog.pg_ddl Richard Huxton
  • Re: Interesting speed anomaly Tom Lane
  • Interesting speed anomaly Zoltan Boszormenyi
  • Re: Immodest Proposal: pg_catalog.pg_ddl Tom Lane
  • Re: Immodest Proposal: pg_catalog.pg_ddl Andrew Dunstan
  • Re: psql and COPY BINARY Tom Lane
  • Re: ANSI SQL, CASE expression Conformance F262, F263 any info Tom Lane
  • Re: lo function changed in PostgreSQL 8.1.1 Tom Lane
  • Re: Immodest Proposal: pg_catalog.pg_ddl Tom Lane
  • Re: Refactoring psql for backward-compatibility Alvaro Herrera
  • Re: Cost-based optimizers Rod Taylor
  • Re: Refactoring psql for backward-compatibility Andrew Dunstan
  • psql and COPY BINARY Andreas Pflug
  • Re: Refactoring psql for backward-compatibility Martijn van Oosterhout
  • Re: Cost-based optimizers Martijn van Oosterhout
  • Refactoring psql for backward-compatibility David Fetter

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