• 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-04 Chronological Index (1/6)

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

• 11 November 2008
  • [no subject] Unknown
  • [no subject] Unknown
  • [no subject] Unknown
• 01 May 2005
  • Re: [pgsql-advocacy] Increased company involvement Robert Treat
  • Re: [pgsql-advocacy] Increased company involvement Robert Treat
  • pl/Python James William Pye
  • Re: [pgsql-advocacy] Increased company involvement Robert Treat
• 30 April 2005
  • OLAP and PG and deja-vu Mischa Sandberg
  • Re: Output functions with multiple arguments considered harmful elein
  • Re: Output functions with multiple arguments considered James William Pye
  • Re: [pgsql-advocacy] Increased company involvement David Fetter
  • Re: Output functions with multiple arguments considered harmful Tom Lane
  • Re: Output functions with multiple arguments considered harmful elein
  • pg_locks needs a facelift Tom Lane
  • Output functions with multiple arguments considered harmful Tom Lane
  • Re: [pgsql-advocacy] Increased company involvement Robert Treat
  • Re: [pgsql-advocacy] Increased company involvement Bruce Momjian
  • Re: [pgsql-advocacy] Increased company involvement Bruce Momjian
  • Re: Increased company involvement Bruce Momjian
  • Re: [pgsql-advocacy] Increased company involvement Rob Butler
  • Re: [proposal] protocol extension to support loadable stream Neil Conway
  • Re: [pgsql-advocacy] Increased company involvement Kris Jurka
  • Re: [pgsql-advocacy] Increased company involvement Nicolai Petri (lists)
  • Re: Increased company involvement Joshua D. Drake
  • Re: Increased company involvement Jim C. Nasby
  • Re: [pgsql-advocacy] Increased company involvement Jim C. Nasby
  • Re: Increased company involvement Joshua D. Drake
  • Re: Increased company involvement Jim C. Nasby
  • Re: Increased company involvement Joshua D. Drake
  • Re: [pgsql-advocacy] Increased company involvement Kris Jurka
  • Re: Increased company involvement Tom Lane
  • Re: Feature freeze date for 8.1 Matthew T. O'Connor
  • Re: Increased company involvement Bruce Momjian
  • Re: Feature freeze date for 8.1 Marc G. Fournier
  • SPI bug. Tzahi Fadida
  • Re: performance of bitmap scans in nested loop joins Sergey E. Koposov
• 29 April 2005
  • Re: Feature freeze date for 8.1 Jim C. Nasby
  • Re: Feature freeze date for 8.1 Christopher Browne
  • Re: Increased company involvement Andrew Dunstan
  • Re: [proposal] protocol extension to support loadable stream filters Alvaro Herrera
  • Re: performance of bitmap scans in nested loop joins Tom Lane
  • Re: [GENERAL] Returning a RECORD, not SETOF RECORD Tom Lane
  • Re: [GENERAL] Returning a RECORD, not SETOF RECORD Michael Fuhr
  • Re: Feature freeze date for 8.1 Marc G. Fournier
  • Re: Feature freeze date for 8.1 Tom Lane
  • Re: pg_restore stuck in a loop? Tom Lane
  • Re: Feature freeze date for 8.1 Bruno Wolff III
  • Re: Feature freeze date for 8.1 Marc G. Fournier
  • Re: Feature freeze date for 8.1 Matthew T. O'Connor
  • Re: Feature freeze date for 8.1 Bruno Wolff III
  • Re: [GENERAL] Returning a RECORD, not SETOF RECORD Tom Lane
  • Re: [proposal] protocol extension to support loadable stream filters Tom Lane
  • performance of bitmap scans in nested loop joins Sergey E. Koposov
  • Re: Feature freeze date for 8.1 Bruce Momjian
  • Re: Feature freeze date for 8.1 Tom Lane
  • Re: pg_restore stuck in a loop? Rod Taylor
  • PseudoPartitioning and agregates Sokolov Yura
  • Re: [GENERAL] Returning a RECORD, not SETOF RECORD Thomas Hallgren
  • Re: Feature freeze date for 8.1 Christopher Browne
  • Re: [PERFORM] Distinct-Sampling (Gibbons paper) for Postgres Josh Berkus
  • Re: Distinct-Sampling (Gibbons paper) for Postgres a3a18850
  • Re: [pgsql-advocacy] Increased company involvement Bruce Momjian
  • Re: [COMMITTERS] pgsql: Implement sharable row-level locks, and use them for foreign key Tom Lane
  • Re: [pgsql-advocacy] Increased company involvement Josh Berkus
  • Re: [proposal] protocol extension to support loadable stream filters Brent Verner
• 28 April 2005
  • Re: [COMMITTERS] pgsql: Implement sharable row-level locks, and use them for foreign key Alvaro Herrera
  • Re: [pgsql-advocacy] Increased company involvement Andy Astor
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Marko Ristola
  • Re: [JDBC] Statement Timeout and Locking Markus Schaber
  • Re: Feature freeze date for 8.1 Andreas Pflug
  • Re: [JDBC] Statement Timeout and Locking Tom Lane
  • Re: [pgsql-advocacy] Increased company involvement Magnus Hagander
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Mischa Sandberg
  • Re: [pgsql-advocacy] Increased company involvement Robert Treat
  • Re: Feature freeze date for 8.1 Rob Butler
  • Re: Feature freeze date for 8.1 Bruno Wolff III
  • Re: [proposal] protocol extension to support loadable stream filters Tom Lane
  • Feature freeze date for 8.1 Bruce Momjian
  • Re: [pgsql-advocacy] Increased company involvement Bruce Momjian
  • Re: [pgsql-advocacy] Increased company involvement Hannu Krosing
  • Re: Increased company involvement Thomas Hallgren
  • Re: pg_restore stuck in a loop? Tom Lane
  • Re: [pgsql-advocacy] Increased company involvement Bruce Momjian
  • Re: [pgsql-advocacy] Increased company involvement Joshua D. Drake
  • Re: DO INSTEAD and conditional rules Zeugswetter Andreas DAZ SD
  • Re: [pgsql-advocacy] Increased company involvement Bruce Momjian
  • Re: [pgsql-advocacy] Increased company involvement Christopher Kings-Lynne
  • Re: [pgsql-advocacy] Increased company involvement Joshua D. Drake
  • Increased company involvement Bruce Momjian
  • Re: Tablepartitioning: Will it be supported in Future? Neil Conway
  • Re: Tablepartitioning: Will it be supported in Future? Bruce Momjian
  • Re: Tablepartitioning: Will it be supported in Future? Christopher Kings-Lynne
  • Re: pg_restore stuck in a loop? Rod Taylor
  • Re: Developer Community Juan Jose Costello Levien
  • Re: PITR bad restore possibility? Rod Taylor
  • Re: Developer Community Jim C. Nasby
  • Re: PITR bad restore possibility? Tom Lane
• 27 April 2005
  • Developer Community Juan Jose Costello Levien
  • Re: [PATCHES] [WIP] shared locks Tom Lane
  • PITR bad restore possibility? Rod Taylor
  • Re: Tablepartitioning: Will it be supported in Future? Hannu Krosing
  • Re: Tablepartitioning: Will it be supported in Future? Josh Berkus
  • Re: Tablepartitioning: Will it be supported in Future? Hannu Krosing
  • Re: Behavior of shared/exclusive row locks Alvaro Herrera
  • Re: Behavior of shared/exclusive row locks Tom Lane
  • Re: Behavior of shared/exclusive row locks Alvaro Herrera
  • Re: [PATCHES] Continue transactions after errors in psql Bruce Momjian
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Greg Stark
  • Re: [PATCHES] Continue transactions after errors in psql Tom Lane
  • Re: [PATCHES] Continue transactions after errors in psql Bruce Momjian
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Dave Held
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Josh Berkus
  • Behavior of shared/exclusive row locks Tom Lane
  • PITR and postmaster.pid Rod Taylor
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Dave Held
  • Re: [proposal] protocol extension to support loadable stream filters Brent Verner
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Andrew Dunstan
  • Re: possible TODO: read-only tables, select from indexes Simon Riggs
  • Re: [PATCHES] Continue transactions after errors in psql Robert Treat
  • Re: [PATCHES] Continue transactions after errors in psql Greg Sabino Mullane
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Simon Riggs
  • Re: bitmapscan test, no success, bs is not faster Pavel Stehule
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Greg Stark
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Mischa Sandberg
  • Re: Disable large objects GUC Christopher Kings-Lynne
  • Re: Disable large objects GUC Tom Lane
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Tom Lane
  • Re: pg_restore stuck in a loop? Tom Lane
  • Re: [proposal] protocol extension to support loadable stream filters Tom Lane
  • Re: DO INSTEAD and conditional rules David Wheeler
  • Disable large objects GUC Christopher Kings-Lynne
  • Re: [proposal] protocol extension to support loadable stream filters Brent Verner
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Rod Taylor
  • Re: DO INSTEAD and conditional rules Jan Wieck
  • Re: [PATCHES] Continue transactions after errors in psql John DeSoi
• 26 April 2005
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Greg Stark
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Rod Taylor
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Greg Stark
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Dave Held
  • Re: DO INSTEAD and conditional rules David Wheeler
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Gurmeet Manku
  • Re: DO INSTEAD and conditional rules Tom Lane
  • Re: DO INSTEAD and conditional rules Tom Lane
  • Re: How to make lazy VACUUM of one table run in several transactions ? Tom Lane
  • Re: DO INSTEAD and conditional rules David Wheeler
  • Re: DO INSTEAD and conditional rules Rob Butler
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Andrew Dunstan
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Simon Riggs
  • populating a table via the COPY command using C code. Mak, Jason
  • Re: Tablepartitioning: Will it be supported in Future? Robert Treat
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Josh Berkus
  • Re: [PERFORM] Bad n_distinct estimation; hacks suggested? Simon Riggs
  • Re: How to make lazy VACUUM of one table run in several Hannu Krosing
  • Re: DO INSTEAD and conditional rules David Wheeler
  • Re: DO INSTEAD and conditional rules David Wheeler
  • Re: DO INSTEAD and conditional rules Tom Lane
  • Re: DO INSTEAD and conditional rules Jan Wieck
  • Re: DO INSTEAD and conditional rules Rob Butler
  • pg_restore stuck in a loop? Rod Taylor
  • Re: DO INSTEAD and conditional rules Tom Lane
  • Re: bitmapscan test, no success, bs is not faster Oleg Bartunov
  • Re: bitmapscan test, no success, bs is not faster Oleg Bartunov
  • Re: DO INSTEAD and conditional rules David Wheeler
  • Re: DO INSTEAD and conditional rules Tom Lane
  • Re: [PATCHES] Continue transactions after errors in psql Tom Lane
  • Re: DO INSTEAD and conditional rules David Wheeler
  • Re: [PATCHES] Continue transactions after errors in psql Andrew Dunstan
  • Re: [PATCHES] Continue transactions after errors in psql Tom Lane
  • Re: bitmapscan test, no success, bs is not faster Tom Lane
  • Re: [PATCHES] Continue transactions after errors in psql Andrew Dunstan
  • Re: [PATCHES] Continue transactions after errors in psql Tom Lane
  • Re: btree_gist regression tests failing in 8.0 branch? Teodor Sigaev
  • Re: [PATCHES] Continue transactions after errors in psql Tom Lane
  • btree_gist regression tests failing in 8.0 branch? Tom Lane
  • Re: [PATCHES] Continue transactions after errors in Philip Warner
  • Re: Continue transactions after errors in psql Harald Fuchs
  • Re: [PATCHES] Continue transactions after errors in psql Joshua D. Drake
  • Re: [PATCHES] Continue transactions after errors in psql Tom Lane
  • Re: [PATCHES] Continue transactions after errors in psql Michael Paesold
  • Re: [PATCHES] Continue transactions after errors in psql Tom Lane

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