Postgres Performance Date Index

• Thread Index

• Re: Optimization of this SQL sentence
  • From: Alexander Staubo
• Re: Optimization of this SQL sentence
  • From: Alexander Staubo
• Re: Optimization of this SQL sentence
  • From: Craig A. James
• Re: Regarding Bitmap Scan
  • From: Dawid Kuroczko
• Re: Regarding Bitmap Scan
  • From: A. Kretschmer
• Regarding Bitmap Scan
  • From: soni de
• Re: Optimization of this SQL sentence (SOLVED)
  • From: Ruben Rubio
• Re: Optimization of this SQL sentence
  • From: Heikki Linnakangas
• Re: Optimization of this SQL sentence
  • From: Alexander Staubo
• Re: Optimization of this SQL sentence
  • From: A. Kretschmer
• Re: Optimization of this SQL sentence
  • From: Ruben Rubio
• Re: Optimization of this SQL sentence
  • From: Ruben Rubio
• Re: Optimization of this SQL sentence
  • From: Gregory S. Williamson
• Optimization of this SQL sentence
  • From: Ruben Rubio
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Shaun Thomas
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Merlin Moncure
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Jim C. Nasby
• Re: measuring shared memory usage on Windows
  • From: Harald Armin Massa
• Re: Hints proposal
  • From: Mark Kirkwood
• measuring shared memory usage on Windows
  • From: Harald Armin Massa
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Hints proposal
  • From: Shaun Thomas
• Re: Hints proposal
  • From: Bruce Momjian
• Re: Hints proposal
  • From: Brian Hurt
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Merlin Moncure
• Re: Hints proposal
  • From: Csaba Nagy
• Re: measuring shared memory usage on Windows
  • From: David Boreham
• Re: measuring shared memory usage on Windows
  • From: David Boreham
• Re: Hints proposal
  • From: Mark Kirkwood
• Re: measuring shared memory usage on Windows
  • From: Magnus Hagander
• Re: measuring shared memory usage on Windows
  • From: Harald Armin Massa
• Re: measuring shared memory usage on Windows
  • From: Magnus Hagander
• Re: measuring shared memory usage on Windows
  • From: Harald Armin Massa
• Re: Hints proposal
  • From: mark
• Re: measuring shared memory usage on Windows
  • From: Magnus Hagander
• measuring shared memory usage on Windows
  • From: Harald Armin Massa
• Re: Hints proposal
  • From: Craig A. James
• Re: Hints proposal
  • From: Craig A. James
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Tom Lane
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: [ADMIN] autovacuum on a -mostly- r/o table
  • From: Tobias Brox
• Re: [ADMIN] autovacuum on a -mostly- r/o table
  • From: Matthew T. O'Connor
• Re: [ADMIN] autovacuum on a -mostly- r/o table
  • From: Tobias Brox
• Re: [HACKERS] Hints proposal
  • From: Mischa Sandberg
• Re: [HACKERS] Hints proposal
  • From: Tom Lane
• Re: [HACKERS] Hints proposal
  • From: Alvaro Herrera
• Re: [HACKERS] Hints proposal
  • From: Jim C. Nasby
• Re: [HACKERS] Hints proposal
  • From: Josh Berkus
• Re: [HACKERS] Hints proposal
  • From: Josh Berkus
• Re: [HACKERS] Hints proposal
  • From: Bucky Jordan
• Re: [HACKERS] Hints proposal
  • From: Gregory Stark
• Re: [HACKERS] Hints proposal
  • From: Tom Lane
• Re: [HACKERS] Hints proposal
  • From: Jim C. Nasby
• Re: [HACKERS] Hints proposal
  • From: Zeugswetter Andreas ADI SD
• Re: Hints proposal
  • From: Christopher Browne
• Re: Hints proposal
  • From: Jeff Davis
• Re: FW: Simple join optimized badly?
  • From: Mark Kirkwood
• Re: Hints proposal
  • From: Jeff Davis
• Re: FW: Simple join optimized badly?
  • From: Mark Kirkwood
• Re: [HACKERS] Hints proposal
  • From: Alvaro Herrera
• Re: Hints proposal
  • From: Richard Broersma Jr
• Re: Hints proposal
  • From: Tom Lane
• Re: [HACKERS] Hints proposal
  • From: Bucky Jordan
• Re: Hints proposal
  • From: Arjen van der Meijden
• Re: [HACKERS] Hints proposal
  • From: Josh Berkus
• Re: Hints proposal
  • From: Jim C. Nasby
• Re: [HACKERS] Hints proposal
  • From: Jim C. Nasby
• Re: Hints proposal
  • From: Jeff Davis
• Re: [HACKERS] Hints proposal
  • From: Andrew Sullivan
• Re: Scrub one large table against another
  • From: Tom Lane
• Re: Scrub one large table against another
  • From: Brendan Curran
• Re: FW: Simple join optimized badly?
  • From: Scott Marlowe
• Re: Hints proposal
  • From: Csaba Nagy
• Re: [HACKERS] Hints proposal
  • From: Tom Lane
• Re: [HACKERS] Hints proposal
  • From: Csaba Nagy
• Re: Hints proposal
  • From: Jim C. Nasby
• Re: Hints proposal
  • From: Jim C. Nasby
• Re: [HACKERS] Hints proposal
  • From: Josh Berkus
• Re: Hints proposal
  • From: Jeff Davis
• Re: [HACKERS] Hints proposal
  • From: Josh Berkus
• Re: Hints proposal
  • From: Bucky Jordan
• Re: FW: Simple join optimized badly?
  • From: Jim C. Nasby
• Re: Hints proposal
  • From: Csaba Nagy
• Re: [HACKERS] Hints proposal
  • From: Jim C. Nasby
• Re: Hints proposal
  • From: Tom Lane
• Re: Hints proposal
  • From: Merlin Moncure
• Re: Hints proposal
  • From: Heikki Linnakangas
• Re: Hints proposal
  • From: Tom Lane
• Re: Hints proposal
  • From: Joshua Marsh
• Re: Hints proposal
  • From: Bruce Momjian
• Hints proposal
  • From: Jim C. Nasby
• Re: FW: Simple join optimized badly?
  • From: Tom Lane
• Re: FW: Simple join optimized badly?
  • From: Jim C. Nasby
• Re: FW: Simple join optimized badly?
  • From: Mark Kirkwood
• FW: Simple join optimized badly?
  • From: H.J. Sanders
• Re: Scrub one large table against another (vmstat output)
  • From: Markus Schaber
• Re: Scrub one large table against another
  • From: Jim C. Nasby
• Collect stats during seqscan (was: Simple join optimized badly?)
  • From: Jim C. Nasby
• Re: Scrub one large table against another (vmstat output)
  • From: Brendan Curran
• Re: Scrub one large table against another
  • From: Brendan Curran
• Re: Simple join optimized badly?
  • From: Mark Lewis
• Re: Simple join optimized badly?
  • From: Bruce Momjian
• Re: Simple join optimized badly?
  • From: Heikki Linnakangas
• Re: Simple join optimized badly?
  • From: Bucky Jordan
• Re: Simple join optimized badly?
  • From: Brian Herlihy
• Re: Scrub one large table against another
  • From: Tom Lane
• Re: Simple join optimized badly?
  • From: Tom Lane
• Re: Simple join optimized badly?
  • From: Brian Herlihy
• Re: Scrub one large table against another
  • From: Jim C. Nasby
• Re: Simple join optimized badly?
  • From: Mark Kirkwood
• Re: Simple join optimized badly?
  • From: Mark Kirkwood
• Re: Scrub one large table against another
  • From: Brendan Curran
• Re: Scrub one large table against another
  • From: Tom Lane
• Re: Scrub one large table against another
  • From: Brendan Curran
• Re: Scrub one large table against another
  • From: Tom Lane
• Scrub one large table against another
  • From: Brendan Curran
• Re: Simple join optimized badly?
  • From: Jim C. Nasby
• Re: long running transactions
  • From: Tobias Brox
• Re: long running transactions
  • From: Tom Lane
• Re: long running transactions
  • From: Tobias Brox
• Re: long running transactions
  • From: Tom Lane
• Re: long running transactions
  • From: Tobias Brox
• Re: Simple join optimized badly?
  • From: Josh Berkus
• Re: long running transactions
  • From: Tom Lane
• Re: long running transactions
  • From: Tobias Brox
• Re: long running transactions
  • From: Tom Lane
• Re: long running transactions
  • From: Tobias Brox
• Re: long running transactions
  • From: Tom Lane
• Re: long running transactions
  • From: Tobias Brox
• Re: long running transactions
  • From: Tobias Brox
• Re: Simple join optimized badly?
  • From: Bruno Wolff III
• Re: long running transactions
  • From: Tom Lane
• long running transactions
  • From: Tobias Brox
• Re: Simple join optimized badly?
  • From: Joshua D. Drake
• Re: Simple join optimized badly?
  • From: Joshua D. Drake
• Re: Simple join optimized badly?
  • From: Joshua D. Drake
• Re: Simple join optimized badly?
  • From: Jim C. Nasby
• Re: Simple join optimized badly?
  • From: Steinar H. Gunderson
• Re: Postgre 8.0 Installation - Issues
  • From: Jim C. Nasby
• Re: Simple join optimized badly?
  • From: Tom Lane
• Re: Simple join optimized badly?
  • From: Jim C. Nasby
• Re: Simple join optimized badly?
  • From: Jim C. Nasby
• Re: Simple join optimized badly?
  • From: Jim C. Nasby
• Postgre 8.0 Installation - Issues
  • From: Ravindran G - TLS, Chennai.
• Re: odd variances in count(*) times
  • From: Merlin Moncure
• Re: Simple join optimized badly?
  • From: Joshua D. Drake
• Re: Simple join optimized badly?
  • From: Craig A. James
• Re: Simple join optimized badly?
  • From: Brian Herlihy
• Re: Simple join optimized badly?
  • From: Tom Lane
• Re: Simple join optimized badly?
  • From: Joshua D. Drake
• Re: Simple join optimized badly?
  • From: Tom Lane
• Re: Simple join optimized badly?
  • From: Jim C. Nasby
• Re: Simple join optimized badly?
  • From: Tobias Brox
• Re: autovacuum not working?
  • From: Jim C. Nasby
• Re: odd variances in count(*) times
  • From: Jim C. Nasby
• Re: Simple join optimized badly?
  • From: Jim C. Nasby
• Re: Simple join optimized badly?
  • From: Scott Marlowe
• Re: Simple join optimized badly?
  • From: Chris Browne
• Re: odd variances in count(*) times
  • From: Steinar H. Gunderson
• Re: odd variances in count(*) times
  • From: Merlin Moncure
• Re: odd variances in count(*) times
  • From: Stephen Frost
• odd variances in count(*) times
  • From: Merlin Moncure
• Re: Simple join optimized badly?
  • From: Tom Lane
• Re: Simple join optimized badly?
  • From: Josh Berkus
• Re: autovacuum not working?
  • From: Medora Schauer
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Merlin Moncure
• Re: autovacuum not working?
  • From: Bill Moran
• autovacuum not working?
  • From: Medora Schauer
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Merlin Moncure
• Re: Simple join optimized badly?
  • From: Tom Lane
• Re: Simple join optimized badly?
  • From: Mark Kirkwood
• Re: Simple join optimized badly?
  • From: Chris Browne
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Jim C. Nasby
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Jim C. Nasby
• Re: Simple join optimized badly?
  • From: Craig A. James
• Re: Simple join optimized badly?
  • From: Craig A. James
• Re: Simple join optimized badly?
  • From: Mark Kirkwood
• Re: Simple join optimized badly?
  • From: Bruce Momjian
• Re: Simple join optimized badly?
  • From: Tom Lane
• Re: Simple join optimized badly?
  • From: Craig A. James
• Re: Simple join optimized badly?
  • From: Josh Berkus
• Re: Simple join optimized badly?
  • From: Jim Nasby
• Re: Simple join optimized badly?
  • From: Denis Lussier
• Re: Simple join optimized badly?
  • From: Tom Lane
• Simple join optimized badly?
  • From: Craig A. James
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Merlin Moncure
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Scott Marlowe
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: slow queue-like empty table
  • From: Jim Nasby
• Re: Unsubscribe
  • From: Jim Nasby
• Re: Unsubscribe
  • From: Jim Nasby
• Re: Unsubscribe
  • From: Jim Nasby
• Re: any hope for my big query?
  • From: Jim Nasby
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Tom Lane
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Merlin Moncure
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Tom Lane
• Re: UPDATE becomes mired / win32
  • From: Tom Lane
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Merlin Moncure
• Re: UPDATE becomes mired / win32
  • From: Steve Peterson
• Re: UPDATE becomes mired / win32
  • From: Steve Peterson
• Re: pg_trgm indexes giving bad estimations?
  • From: Tom Lane
• pg_trgm indexes giving bad estimations?
  • From: Ben
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: any hope for my big query?
  • From: Ben
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Merlin Moncure
• Re: Multi-key index not beeing used - bug?
  • From: Tobias Brox
• Re: Multi-key index not beeing used - bug?
  • From: Tom Lane
• Re: UPDATE becomes mired / win32
  • From: Tom Lane
• Re: Unsubscribe
  • From: Michael Stone
• Re: Multi-key index not beeing used - bug?
  • From: Graham Davis
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: UPDATE becomes mired / win32
  • From: me
• Multi-key index not beeing used - bug?
  • From: Tobias Brox
• UPDATE becomes mired / win32
  • From: Steve Peterson
• Re: Poor performance on very simple query ?
  • From: Markus Schaber
• Re: Unsubscribe
  • From: Geoffrey
• Re: Unsubscribe
  • From: Steve Atkins
• Re: Unsubscribe
  • From: Csaba Nagy
• Re: Unsubscribe
  • From: Mark Lewis
• Re: Unsubscribe
  • From: Joshua D. Drake
• Re: Unsubscribe
  • From: Joshua D. Drake
• Re: Unsubscribe
  • From: D'Arcy J.M. Cain
• Re: Unsubscribe
  • From: Bruno Wolff III
• Re: Unsubscribe
  • From: Csaba Nagy
• Re: Unsubscribe
  • From: Joshua D. Drake
• Re: Unsubscribe
  • From: Joshua D. Drake
• Re: Unsubscribe
  • From: Nolan Cafferky
• Re: Unsubscribe
  • From: Tobias Brox
• Re: Unsubscribe
  • From: Joshua D. Drake
• Re: Unsubscribe
  • From: Bruno Wolff III
• Re: simple case using index on windows but not on linux
  • From: simon godden
• Re: simple case using index on windows but not on linux
  • From: simon godden
• Re: simple case using index on windows but not on linux
  • From: Dave Dutcher
• Re: simple case using index on windows but not on linux
  • From: Richard Huxton
• Re: PostgreSQL Caching
  • From: Brad Nicholson
• Re: simple case using index on windows but not on linux
  • From: simon godden
• Re: PostgreSQL Caching
  • From: Brad Nicholson
• Re: simple case using index on windows but not on linux
  • From: Richard Huxton
• Re: PostgreSQL Caching
  • From: Dave Dutcher
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Markus Schaber
• Re: slow queue-like empty table
  • From: Tobias Brox
• Re: simple case using index on windows but not on linux
  • From: Richard Huxton
• Re: simple case using index on windows but not on linux
  • From: Richard Huxton
• Re: simple case using index on windows but not on linux
  • From: simon godden
• Re: simple case using index on windows but not on linux
  • From: simon godden
• Re: simple case using index on windows but not on linux
  • From: Heikki Linnakangas
• Unsubscribe
  • From: Luc Delgado
• simple case using index on windows but not on linux
  • From: simon godden
• Re: PostgreSQL Caching
  • From: Adnan DURSUN
• Re: PostgreSQL Caching
  • From: Tomeh, Husam
• Re: Forcing the use of particular execution plans
  • From: Jim C. Nasby
• Re: Forcing the use of particular execution plans
  • From: Ron Mayer
• Re: PostgreSQL Caching
  • From: Adnan DURSUN
• Re: BUG #2658: Query not using index
  • From: Tom Lane
• Re: PostgreSQL Caching
  • From: Tomeh, Husam
• Re: BUG #2658: Query not using index
  • From: Mark Lewis
• PostgreSQL Caching
  • From: Adnan DURSUN
• Re: BUG #2658: Query not using index
  • From: Graham Davis
• Re: BUG #2658: Query not using index
  • From: Mark Lewis
• Re: BUG #2658: Query not using index
  • From: Graham Davis
• Re: BUG #2658: Query not using index
  • From: Mark Lewis
• Re: BUG #2658: Query not using index
  • From: Graham Davis
• Re: BUG #2658: Query not using index
  • From: Tom Lane
• Re: BUG #2658: Query not using index
  • From: Bruno Wolff III
• Re: BUG #2658: Query not using index
  • From: Graham Davis
• Re: BUG #2658: Query not using index
  • From: Chris Browne
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Merlin Moncure
• Re: BUG #2658: Query not using index
  • From: Graham Davis
• Re: BUG #2658: Query not using index
  • From: Graham Davis
• Re: BUG #2658: Query not using index
  • From: Chris Browne
• Re: BUG #2658: Query not using index
  • From: Graham Davis
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Unsubscribe
  • From: Carlo Stonebanks
• Re: Unsubscribe
  • From: felix
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Alex Stapleton
• Re: Poor performance on very simple query ?
  • From: Darcy Buskermolen
• Re: Poor performance on very simple query ?
  • From: Darcy Buskermolen
• Re: Performance Optimization for Dummies 2 - the SQL
  • From: Merlin Moncure
• Re: Unsubscribe
  • From: Geoffrey
• Re: Poor performance on very simple query ?
  • From: Tom Lane
• Re: Poor performance on very simple query ?
  • From: Guillaume Cottenceau
• Re: Poor performance on very simple query ?
  • From: Arnaud Lesauvage
• Re: Poor performance on very simple query ?
  • From: Tobias Brox
• Re: Poor performance on very simple query ?
  • From: Arnaud Lesauvage
• Re: Poor performance on very simple query ?
  • From: Tobias Brox
• Re: Poor performance on very simple query ?
  • From: Tobias Brox
• Re: Poor performance on very simple query ?
  • From: Alexander Staubo
• Re: Poor performance on very simple query ?
  • From: Arnaud Lesauvage
• Re: Poor performance on very simple query ?
  • From: Steinar H. Gunderson
• Poor performance on very simple query ?
  • From: Arnaud Lesauvage
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Performance Optimization for Dummies 2 - the SQL
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Markus Schaber
• Re: Performace Optimization for Dummies
  • From: Markus Schaber
• Re: High CPU Load
  • From: Jérôme BENOIS
• Re: Forcing the use of particular execution plans
  • From: Tim Truman
• Re: Forcing the use of particular execution plans
  • From: Tom Lane
• Re: Forcing the use of particular execution plans
  • From: Tim Truman
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: selecting data from information_schema.columns
  • From: Jim Nasby
• Re: selecting data from information_schema.columns
  • From: Steve Martin
• Re: Unsubscribe
  • From: Markus Schaber
• Re: selecting data from information_schema.columns performance.
  • From: Jim C. Nasby
• Re: Table not getting vaccumed.
  • From: Jim C. Nasby
• Unsubscribe
  • From: uwcssa
• Re: How much memory in 32 bits Architecture to Shared Buffers is Possible
  • From: Marcelo Costa
• Re: How much memory in 32 bits Architecture to Shared Buffers
  • From: Joshua D. Drake
• Re: archive wal's failure and load increase.
  • From: Simon Riggs
• Re: Optimizing queries
  • From: Simon Riggs
• Re: any hope for my big query?
  • From: Shaun Thomas
• How much memory in 32 bits Architecture to Shared Buffers is Possible
  • From: Marcelo Costa
• Re: PostgreSQL runs a query much slower than BDE and
  • From: Simon Riggs
• Re: selecting data from information_schema.columns performance.
  • From: Tom Lane
• selecting data from information_schema.columns performance.
  • From: Steve Martin
• Re: Table not getting vaccumed.
  • From: Tom Lane
• Re: how to optimize postgres 8.1
  • From: Markus Schaber
• Table not getting vaccumed.
  • From: Nimesh Satam
• Re: Postgres locking up?
  • From: Robert Becker Cope
• Re: cont. how to optimize postgres 8.1
  • From: Tom Lane
• cont. how to optimize postgres 8.1
  • From: gurkan
• Re: [NOVICE] Postgres locking up?
  • From: Tom Lane
• Re: Postgres locking up?
  • From: Andrew Sullivan
• Postgres locking up?
  • From: Brian Hurt
• Re: how to optimize postgres 8.1
  • From: Tom Lane
• how to optimize postgres 8.1
  • From: gurkan
• Re: archive wal's failure and load increase.
  • From: Tom Lane
• Re: any hope for my big query?
  • From: Jim C. Nasby
• Re: archive wal's failure and load increase.
  • From: Simon Riggs
• Re: Performace Optimization for Dummies
  • From: Merlin Moncure
• Re: archive wal's failure and load increase.
  • From: Tom Lane
• Re: Performace Optimization for Dummies
  • From: Bill Moran
• Re: Performace Optimization for Dummies
  • From: Markus Schaber
• Re: Performace Optimization for Dummies
  • From: Markus Schaber
• Re: any hope for my big query?
  • From: Simon Riggs
• Re: archive wal's failure and load increase.
  • From: Simon Riggs
• Re: Performace Optimization for Dummies
  • From: Simon Riggs
• Re: any hope for my big query?
  • From: Edoardo Ceccarelli
• Re: Performace Optimization for Dummies
  • From: Heikki Linnakangas
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Tom Lane
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Matthew Nuzum
• Re: any hope for my big query?
  • From: Jim C. Nasby
• Re: Performace Optimization for Dummies
  • From: Jim C. Nasby
• any hope for my big query?
  • From: Ben
• Re: archive wal's failure and load increase.
  • From: Tom Lane
• Re: Performace Optimization for Dummies
  • From: Steve Atkins
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Merlin Moncure
• Re: slow queue-like empty table
  • From: Andrew Sullivan
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• archive wal's failure and load increase.
  • From: Cedric Boudin
• Re: Performace Optimization for Dummies
  • From: Merlin Moncure
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Matthew Nuzum
• RES: Performace Optimization for Dummies
  • From: Leandro Guimarães dos Santos
• [no subject]
  • From: Jim C. Nasby
• Re: Performace Optimization for Dummies
  • From: Jim C. Nasby
• Re: Performace Optimization for Dummies
  • From: Jim C. Nasby
• Re: Performace Optimization for Dummies
  • From: Jim C. Nasby
• Re: Performace Optimization for Dummies
  • From: Dave Dutcher
• Re: Performace Optimization for Dummies
  • From: Steve Atkins
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Problems with inconsistant query performance.
  • From: Bill Moran
• Re: Performace Optimization for Dummies
  • From: Merlin Moncure
• Re: Performace Optimization for Dummies
  • From: Joshua D. Drake
• Performace Optimization for Dummies
  • From: Carlo Stonebanks
• Re: Problems with inconsistant query performance.
  • From: Jim C. Nasby
• Re: Problems with inconsistant query performance.
  • From: Bill Moran
• Re: Problems with inconsistant query performance.
  • From: Matthew Schumacher
• Re: Problems with inconsistant query performance.
  • From: Marcin Mank
• Re: slow i/o
  • From: Jignesh K. Shah
• Re: slow queue-like empty table
  • From: Csaba Nagy
• Re: autovacuum on a -mostly- r/o table
  • From: Edoardo Ceccarelli
• Re: slow queue-like empty table
  • From: Tobias Brox
• slow queue-like empty table
  • From: Tobias Brox
• Re: Problems with inconsistant query performance.
  • From: Jim C. Nasby
• Re: Problems with inconsistant query performance.
  • From: Matthew Schumacher
• Re: Problems with inconsistant query performance.
  • From: Jim C. Nasby
• Re: Problems with inconsistant query performance.
  • From: Matthew Schumacher
• Re: Problems with inconsistant query performance.
  • From: Jim C. Nasby
• Re: autovacuum on a -mostly- r/o table
  • From: Bill Moran
• Re: Forcing the use of particular execution plans
  • From: Jim C. Nasby
• Re: Merge Join vs Nested Loop
  • From: Tobias Brox
• Problems with inconsistant query performance.
  • From: Matthew Schumacher
• Re: [ADMIN] autovacuum on a -mostly- r/o table
  • From: Matthew T. O'Connor
• Re: autovacuum on a -mostly- r/o table
  • From: Rod Taylor
• Re: autovacuum on a -mostly- r/o table
  • From: Tobias Brox
• Re: autovacuum on a -mostly- r/o table
  • From: Edoardo Ceccarelli
• Re: autovacuum on a -mostly- r/o table
  • From: Edoardo Ceccarelli
• Re: autovacuum on a -mostly- r/o table
  • From: Bill Moran
• Re: autovacuum on a -mostly- r/o table
  • From: Csaba Nagy
• Re: autovacuum on a -mostly- r/o table
  • From: Tobias Brox
• Re: autovacuum on a -mostly- r/o table
  • From: Alan Hodgson
• autovacuum on a -mostly- r/o table
  • From: Edoardo Ceccarelli
• Re: Forcing the use of particular execution plans
  • From: Dave Dutcher
• Re: Merge Join vs Nested Loop
  • From: Tobias Brox
• Re: Merge Join vs Nested Loop
  • From: Scott Marlowe
• Re: Merge Join vs Nested Loop
  • From: Tobias Brox
• Re: Merge Join vs Nested Loop
  • From: Scott Marlowe
• Re: Merge Join vs Nested Loop
  • From: Tobias Brox
• Re: Merge Join vs Nested Loop
  • From: Scott Marlowe
• Re: Forcing the use of particular execution plans
  • From: Jochem van Dieten
• Re: Merge Join vs Nested Loop
  • From: Tobias Brox
• Forcing the use of particular execution plans
  • From: Tim Truman
• Re: PostgreSQL and sql-bench
  • From: Jim Nasby
• Re: Confusion and Questions about blocks read
  • From: Jim Nasby
• Re: Decreasing BLKSZ
  • From: Jim Nasby
• Re: IN not handled very well?
  • From: Jim Nasby
• Re: Update on high concurrency OLTP application and Postgres
  • From: Jim Nasby
• Re: slow i/o
  • From: Junaili Lie
• Re: Decreasing BLKSZ
  • From: Markus Schaber
• Re: Decreasing BLKSZ
  • From: Bucky Jordan
• Re: Merge Join vs Nested Loop
  • From: Tom Lane
• Re: Decreasing BLKSZ
  • From: Marc Morin
• Re: Decreasing BLKSZ
  • From: Bucky Jordan
• Merge Join vs Nested Loop
  • From: Tobias Brox
• Re: Decreasing BLKSZ
  • From: Marc Morin
• Re: Decreasing BLKSZ
  • From: Mark Lewis
• Re: Decreasing BLKSZ
  • From: Tom Lane
• Re: Decreasing BLKSZ
  • From: Marc Morin
• Re: Decreasing BLKSZ
  • From: Markus Schaber
• Decreasing BLKSZ
  • From: Marc Morin
• Re: PostgreSQL and sql-bench
  • From: yoav x
• Re: Large tables (was: RAID 0 not as fast as
  • From: Luke Lonergan
• Re: Multi-processor question
  • From: Markus Schaber
• Multi-processor question
  • From: Kjell Tore Fossbakk
• Re: IN not handled very well?
  • From: Ben
• Re: IN not handled very well?
  • From: Tom Lane
• IN not handled very well?
  • From: Ben
• Re: Large tables (was: RAID 0 not as fast as
  • From: Ron Mayer
• Re: Opteron vs. Xeon "benchmark"
  • From: Dave Cramer
• Re: Update on high concurrency OLTP application and Postgres
  • From: Cosimo Streppone
• Re: Opteron vs. Xeon "benchmark"
  • From: Guido Neitzer
• Re: Opteron vs. Xeon "benchmark"
  • From: Dave Cramer
• Re: Opteron vs. Xeon "benchmark"
  • From: Guido Neitzer
• Re: Confusion and Questions about blocks read
  • From: Markus Schaber
• Re: recommended benchmarks
  • From: Denis Lussier
• Re: Why is it choosing a different plan?
  • From: Anthony Presley
• Re: Why is it choosing a different plan?
  • From: Anthony Presley
• Why is it choosing a different plan?
  • From: Anthony Presley
• Re: Opteron vs. Xeon "benchmark"
  • From: mark
• Re: Opteron vs. Xeon "benchmark"
  • From: Arjen van der Meijden
• Re: Confusion and Questions about blocks read
  • From: Alex Turner
• Re: recommended benchmarks
  • From: Bucky Jordan
• Re: Opteron vs. Xeon "benchmark"
  • From: Vivek Khera
• Re: recommended benchmarks
  • From: Brad Nicholson
• recommended benchmarks
  • From: Charles Sprickman
• Re: Confusion and Questions about blocks read
  • From: Alex Turner
• Re: Confusion and Questions about blocks read
  • From: Tom Lane
• Confusion and Questions about blocks read
  • From: Alex Turner
• Re: Large tables (was: RAID 0 not as fast as
  • From: Jim C. Nasby
• Re: Large tables (was: RAID 0 not as fast as
  • From: Jim C. Nasby
• Re: Opteron vs. Xeon "benchmark"
  • From: nicky
• Re: Large tables (was: RAID 0 not as fast as
  • From: Markus Schaber
• Re: Opteron vs. Xeon "benchmark"
  • From: Arjen van der Meijden
• Opteron vs. Xeon "benchmark"
  • From: Hannes Dorbath
• Re: High CPU Load
  • From: Jérôme BENOIS
• Re: Large tables (was: RAID 0 not as fast as
  • From: Luke Lonergan
• Re: Large tables (was: RAID 0 not as fast as
  • From: mark
• Re: Large tables (was: RAID 0 not as fast as
  • From: Bruce Momjian
• Re: Large tables (was: RAID 0 not as fast as
  • From: Guy Thornley
• Re: Large tables (was: RAID 0 not as fast as
  • From: Luke Lonergan
• Re: PostgreSQL and sql-bench
  • From: Arjen van der Meijden
• Re: PostgreSQL and sql-bench
  • From: Jim C. Nasby
• Re: Large tables (was: RAID 0 not as fast as
  • From: Markus Schaber
• Re: Large tables (was: RAID 0 not as fast as
  • From: Bucky Jordan
• Re: Large tables (was: RAID 0 not as fast as
  • From: Markus Schaber
• Re: Large tables (was: RAID 0 not as fast as
  • From: Mark Lewis
• Re: Large tables (was: RAID 0 not as fast as
  • From: Bucky Jordan
• Re: PostgreSQL and sql-bench
  • From: Jeff Davis
• Re: PostgreSQL and sql-bench
  • From: Tom Lane
• Re: PostgreSQL and sql-bench
  • From: Guido Neitzer
• Re: PostgreSQL and sql-bench
  • From: Mark Lewis
• Re: PostgreSQL and sql-bench
  • From: Brad Nicholson
• PostgreSQL and sql-bench
  • From: yoav x
• Re: Large tables (was: RAID 0 not as fast as
  • From: Markus Schaber
• Re: Large tables (was: RAID 0 not as fast as
  • From: Luke Lonergan
• Re: running benchmark test on a 50GB database
  • From: Jim C. Nasby
• Re: Large tables (was: RAID 0 not as fast as
  • From: Ron
• Re: Large tables (was: RAID 0 not as fast as
  • From: Markus Schaber
• Re: Large tables (was: RAID 0 not as fast as
  • From: Luke Lonergan
• Re: running benchmark test on a 50GB database
  • From: Chris Mair
• Re: running benchmark test on a 50GB database
  • From: Dave Dutcher
• running benchmark test on a 50GB database
  • From: Nuno Alves
• Re: Update on high concurrency OLTP application and Postgres
  • From: Cosimo Streppone
• Re: Update on high concurrency OLTP application and Postgres 8 tuning
  • From: Andrew Sullivan
• Update on high concurrency OLTP application and Postgres 8 tuning
  • From: Cosimo Streppone
• Re: Large tables (was: RAID 0 not as fast as
  • From: Markus Schaber
• Re: Pipelined functions in Postgres
  • From: Jeff Davis
• Re: Pipelined functions in Postgres
  • From: Shoaib Mir
• Re: Pipelined functions in Postgres
  • From: Milen Kulev
• Re: Pipelined functions in Postgres
  • From: Milen Kulev
• Re: Pipelined functions in Postgres
  • From: Talha Khan
• Re: Pipelined functions in Postgres
  • From: Shoaib Mir
• Pipelined functions in Postgres
  • From: Milen Kulev
• Re: Optimizing DELETE
  • From: Ivan Voras
• Re: Optimizing DELETE
  • From: Mark Lewis
• Re: Optimizing DELETE
  • From: Rod Taylor
• Re: Optimizing DELETE
  • From: Csaba Nagy
• Re: Large tables (was: RAID 0 not as fast as expected)
  • From: Bucky Jordan
• Optimizing DELETE
  • From: Ivan Voras
• Re: High CPU Load
  • From: Markus Schaber
• Re: High CPU Load
  • From: Jérôme BENOIS
• Re: High CPU Load
  • From: Markus Schaber
• Re: Large tables (was: RAID 0 not as fast as
  • From: Luke Lonergan
• Re: Large tables (was: RAID 0 not as fast as expected)
  • From: mark
• Re: Large tables (was: RAID 0 not as fast as
  • From: Luke Lonergan
• Re: Large tables (was: RAID 0 not as fast as expected)
  • From: Alex Turner
• Re: LIKE query problem
  • From: Marc McIntyre
• Re: LIKE query problem
  • From: Tom Lane
• Re: Large tables (was: RAID 0 not as fast as
  • From: Luke Lonergan
• Re: Large tables (was: RAID 0 not as fast as expected)
  • From: Luke Lonergan
• Re: Vacuums on large busy databases
  • From: Francisco Reyes
• LIKE query problem
  • From: Marc McIntyre
• Re: Large tables (was: RAID 0 not as fast as expected)
  • From: Michael Stone
• Re: Large tables (was: RAID 0 not as fast as expected)
  • From: Alex Turner
• Re: Large tables (was: RAID 0 not as fast as expected)
  • From: Bucky Jordan
• Re: Vacuums on large busy databases
  • From: Jim C. Nasby
• Re: Large tables (was: RAID 0 not as fast as expected)
  • From: Alan Hodgson
• Re: Large tables (was: RAID 0 not as fast as expected)
  • From: Merlin Moncure
• Re: High CPU Load
  • From: Guillaume Smet
• Re: High CPU Load
  • From: Jérôme BENOIS
• Large tables (was: RAID 0 not as fast as expected)
  • From: Bucky Jordan
• Re: High CPU Load
  • From: Jérôme BENOIS
• Re: Poor performance on seq scan
  • From: Guido Neitzer
• Re: Poor performance on seq scan
  • From: Markus Schaber
• Re: Optimize SQL
  • From: Mikael Carneholm
• Re: Partition elimination problem -> Solved
  • From: Milen Kulev
• Re: Partition elimination problem
  • From: Milen Kulev
• Re: Partition elimination problem
  • From: Tom Lane
• Partition elimination problem
  • From: Milen Kulev
• Re: RAID 0 not as fast as expected
  • From: Joshua D. Drake
• Re: RAID 0 not as fast as expected
  • From: Steinar H. Gunderson
• Re: RAID 0 not as fast as expected
  • From: Luke Lonergan
• Re: RAID 0 not as fast as expected
  • From: Luke Lonergan
• Re: Performance of IN (...) vs. = ANY array[...]
  • From: Tom Lane
• Performance of IN (...) vs. = ANY array[...]
  • From: Benjamin Minshall
• Re: RAID 0 not as fast as expected
  • From: Bucky Jordan
• Re: Optimize SQL
  • From: Arjen van der Meijden
• Re: Why the difference in plans ??
  • From: Tom Lane
• Re: Why the difference in plans ??
  • From: Joost Kraaijeveld
• Re: Optimize SQL
  • From: Tom Lane
• Re: RAID 0 not as fast as expected
  • From: Luke Lonergan
• Optimize SQL
  • From: Pallav Kalva
• Re: Why the difference in plans ??
  • From: Tom Lane
• Re: RAID 0 not as fast as expected
  • From: Spiegelberg, Greg
• Re: High CPU Load
  • From: Guillaume Smet
• Lanzamiento www.PortalTPV.com
  • From: Portal TPV
• Re: Vacuums on large busy databases
  • From: Markus Schaber
• Re: High CPU Load
  • From: Markus Schaber
• Why the difference in plans ??
  • From: Joost Kraaijeveld
• Re: RAID 0 not as fast as expected
  • From: Joshua D. Drake
• Re: RAID 0 not as fast as expected
  • From: Joshua D. Drake
• Re: RAID 0 not as fast as expected
  • From: Luke Lonergan
• Re: Vacuums on large busy databases
  • From: Jeff Davis
• Re: Vacuums on large busy databases
  • From: Jeff Davis
• Re: Vacuums on large busy databases
  • From: Michael Stone
• Re: Vacuums on large busy databases
  • From: Jeff Davis
• Re: Vacuums on large busy databases
  • From: Jeff Davis
• Re: Vacuums on large busy databases
  • From: Jeff Davis
• Re: sql-bench
  • From: Steinar H. Gunderson
• Re: sql-bench
  • From: Grega Bremec
• Re: Vacuums on large busy databases
  • From: Michael Stone
• Re: Vacuums on large busy databases
  • From: Dave Cramer
• Re: Vacuums on large busy databases
  • From: Francisco Reyes
• Re: Vacuums on large busy databases
  • From: Francisco Reyes
• Re: Vacuums on large busy databases
  • From: Francisco Reyes
• Re: High CPU Load
  • From: Bucky Jordan
• Re: High CPU Load
  • From: Guillaume Smet
• Re: RAID 0 not as fast as expected
  • From: Scott Marlowe
• Re: Vacuums on large busy databases
  • From: Dave Cramer
• Re: High CPU Load
  • From: Jérôme BENOIS
• Re: High CPU Load
  • From: Jérôme BENOIS
• Re: Vacuums on large busy databases
  • From: Jeff Davis
• Re: RAID 0 not as fast as expected
  • From: Craig A. James
• Re: High CPU Load
  • From: Guillaume Smet
• Re: High CPU Load
  • From: Tom Lane
• Re: High CPU Load
  • From: Jérôme BENOIS
• Re: Vacuums on large busy databases
  • From: Michael Stone
• Re: Vacuums on large busy databases
  • From: Francisco Reyes
• Re: Performance problem with Sarge compared with
  • From: Bruce Momjian
• Re: RAID 0 not as fast as expected
  • From: Alan Hodgson
• Re: RAID 0 not as fast as expected
  • From: Joshua D. Drake
• Re: Vacuums on large busy databases
  • From: Dave Cramer
• RAID 0 not as fast as expected
  • From: Craig A. James
• Re: Vacuums on large busy databases
  • From: Francisco Reyes
• Re: Vacuums on large busy databases
  • From: Francisco Reyes
• Re: High CPU Load
  • From: Evgeny Gridasov
• Re: Vacuums on large busy databases
  • From: Dave Cramer
• Re: High CPU Load
  • From: Scott Marlowe
• Vacuums on large busy databases
  • From: Francisco Reyes
• Re: High CPU Load
  • From: Jérôme BENOIS
• Re: High CPU Load
  • From: Dave Dutcher
• Re: High CPU Load
  • From: Jérôme BENOIS
• Re: High CPU Load
  • From: Guillaume Smet
• Re: High CPU Load
  • From: Scott Marlowe
• Re: Performance With Joins on Large Tables
  • From: Joshua Marsh
• Re: High CPU Load
  • From: Scott Marlowe
• Re: High CPU Load
  • From: Jérôme BENOIS
• Re: High CPU Load
  • From: Tom Lane
• Re: High CPU Load
  • From: Jérôme BENOIS
• Re: High CPU Load
  • From: Guillaume Smet
• High CPU Load
  • From: Jérôme BENOIS
• Re: sql-bench
  • From: Dave Cramer
• Re: sql-bench
  • From: Markus Schaber
• Re: sql-bench
  • From: yoav x
• Re: sql-bench
  • From: Merlin Moncure
• Re: Performance With Joins on Large Tables
  • From: Tom Lane
• Unsubscribe
  • From: Jamal Ghaffour
• Re: Performance With Joins on Large Tables
  • From: Joshua Marsh
• Re: sql-bench
  • From: Tom Lane
• Re: Performance With Joins on Large Tables
  • From: Tom Lane
• Re: Poor performance on seq scan
  • From: Ivan Voras
• Re: Performance With Joins on Large Tables
  • From: Joshua Marsh
• Re: sql-bench
  • From: Scott Marlowe
• Re: Performance With Joins on Large Tables
  • From: Tom Lane
• Re: Unsubscribe
  • From: Geoffrey
• Re: sql-bench
  • From: Tom Lane
• Re: Poor performance on seq scan
  • From: Luke Lonergan
• Re: Performance With Joins on Large Tables
  • From: Joshua Marsh
• Re: Performance With Joins on Large Tables
  • From: Terje Elde
• Re: sql-bench
  • From: Merlin Moncure
• Re: Performance With Joins on Large Tables
  • From: Joshua Marsh
• Re: Query Progress (was: Performance With Joins on Large Tables)
  • From: Joshua Marsh
• Re: Performance With Joins on Large Tables
  • From: Marcin Mank
• Query Progress (was: Performance With Joins on Large Tables)
  • From: Bucky Jordan
• Unsubscribe
  • From: Christoph Nelles
• Re: Performance With Joins on Large Tables
  • From: Jeff Davis
• Re: Performance With Joins on Large Tables
  • From: Joshua Marsh
• Re: Performance With Joins on Large Tables
  • From: Jeff Davis
• Re: sql-bench
  • From: Tom Lane
• Re: Performance With Joins on Large Tables
  • From: Joshua Marsh
• Re: sql-bench
  • From: Mark Lewis
• Re: sql-bench
  • From: Dave Cramer
• Re: sql-bench
  • From: yoav x
• Re: sql-bench
  • From: Dave Cramer
• sql-bench
  • From: yoav x
• Re: Poor performance on seq scan
  • From: Dave Cramer
• Re: Poor performance on seq scan
  • From: Laszlo Nagy
• Re: Performance With Joins on Large Tables
  • From: Jim C. Nasby
• Re:
  • From: Jim C. Nasby
• Re: Bad plan for join to aggregate of join.
  • From: Mischa Sandberg
• Re: Poor performance on seq scan
  • From: Mark Kirkwood
• Re: Bad plan for join to aggregate of join.
  • From: Tom Lane
• Re: Poor performance on seq scan
  • From: Luke Lonergan
• Performance With Joins on Large Tables
  • From: Joshua Marsh