Postgres Performance Date Index

• Thread Index

• Re: truncate a table instead of vaccum full when count(*) is 0
  • From: Gregory Stark
• Re: Best OS for Postgres 8.2
  • From: david
• Re: truncate a table instead of vaccum full when count(*) is 0
  • From: Pomarede Nicolas
• Re: truncate a table instead of vaccum full when count(*) is 0
  • From: Pomarede Nicolas
• Re: truncate a table instead of vaccum full when count(*) is 0
  • From: Heikki Linnakangas
• Re: truncate a table instead of vaccum full when count(*) is 0
  • From: Guillaume Cottenceau
• Re: Best OS for Postgres 8.2
  • From: Steinar H. Gunderson
• Re: Best OS for Postgres 8.2
  • From: Alexander Staubo
• truncate a table instead of vaccum full when count(*) is 0
  • From: Pomarede Nicolas
• Re: Best OS for Postgres 8.2
  • From: Steinar H. Gunderson
• Re: Best OS for Postgres 8.2
  • From: Trygve Laugstøl
• Re: Best OS for Postgres 8.2
  • From: david
• Re: Best OS for Postgres 8.2
  • From: Claus Guttesen
• Re: Best OS for Postgres 8.2
  • From: Heikki Linnakangas
• Re: Best OS for Postgres 8.2
  • From: Claus Guttesen
• Re: Best OS for Postgres 8.2
  • From: david
• Re: Best OS for Postgres 8.2
  • From: 李彦 Ian Li
• Re: Best OS for Postgres 8.2
  • From: Tom Lane
• Re: How to Find Cause of Long Vacuum Times - NOOB Question
  • From: Yudhvir Singh Sidhu
• Re: Best OS for Postgres 8.2
  • From: Greg Smith
• Re: Best OS for Postgres 8.2
  • From: Ron
• Re: Best OS for Postgres 8.2
  • From: Chris
• Re: Best OS for Postgres 8.2
  • From: david
• Re: Best OS for Postgres 8.2
  • From: Chris
• Re: Best OS for Postgres 8.2
  • From: Steve Atkins
• Re: Best OS for Postgres 8.2
  • From: Joshua D. Drake
• Re: Best OS for Postgres 8.2
  • From: Bill Moran
• Re: Best OS for Postgres 8.2
  • From: Joshua D. Drake
• Best OS for Postgres 8.2
  • From: David Levy
• Re: How to Find Cause of Long Vacuum Times - NOOB Question
  • From: Jim Nasby
• Re: Merging large volumes of data
  • From: Tom Lane
• Re: Merging large volumes of data
  • From: Gregory Stark
• Re: Merging large volumes of data
  • From: Andreas Kostyrka
• Merging large volumes of data
  • From: Ambrus Wagner (IJ/ETH)
• Re: Index not being used in sorting of simple table
  • From: Tom Lane
• Re: Index not being used in sorting of simple table
  • From: Robins
• Re: How to Find Cause of Long Vacuum Times - NOOB Question
  • From: Yudhvir Singh Sidhu
• Re: How to Find Cause of Long Vacuum Times - NOOB Question
  • From: Steinar H. Gunderson
• Re: How to Find Cause of Long Vacuum Times - NOOB Question
  • From: Heikki Linnakangas
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Andreas Kostyrka
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Jim Nasby
• Re: How to Find Cause of Long Vacuum Times - NOOB Question
  • From: Yudhvir Singh Sidhu
• Re: How to Find Cause of Long Vacuum Times - NOOB Question
  • From: Steinar H. Gunderson
• How to Find Cause of Long Vacuum Times - NOOB Question
  • From: Yudhvir Singh Sidhu
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Sebastian Hennebrueder
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Steinar H. Gunderson
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Mark Kirkwood
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Greg Smith
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Sebastian Hennebrueder
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Josh Berkus
• Re: Query performance problems with partitioned tables
  • From: Merlin Moncure
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Sebastian Hennebrueder
• Re: Index not being used in sorting of simple table
  • From: Paul Smith
• Re: Index not being used in sorting of simple table
  • From: Tom Lane
• Re: Index not being used in sorting of simple table
  • From: Heikki Linnakangas
• Re: Query performance problems with partitioned tables
  • From: Scott Marlowe
• Index not being used in sorting of simple table
  • From: Paul Smith
• Re: pg_stat_* collection
  • From: Michael Stone
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Michael Stone
• Re: pg_stat_* collection
  • From: Tobias Brox
• Re: pg_stat_* collection
  • From: Greg Smith
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Greg Smith
• Re: Query performance problems with partitioned tables
  • From: Merlin Moncure
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: david
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Carlos Moreno
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: david
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Carlos Moreno
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: david
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Carlos Moreno
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: david
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Carlos Moreno
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: david
• Re: Feature Request --- was: PostgreSQL Performance Tunin g
  • From: Dave Page
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Josh Berkus
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Ron
• Re: pg_stat_* collection
  • From: Jeff Davis
• Re: pg_stat_* collection
  • From: Tobias Brox
• Re: pg_stat_* collection
  • From: Magnus Hagander
• Re: Query performance problems with partitioned tables
  • From: Fei Liu
• Re: pg_stat_* collection
  • From: Alexander Staubo
• pg_stat_* collection
  • From: Greg Smith
• Re: Join vs Subquery
  • From: Tom Lane
• Re: Join vs Subquery
  • From: Gregory Stark
• Re: Intermitent slow queries
  • From: Ron
• Join vs Subquery
  • From: Brian Herlihy
• Re: Intermitent slow queries
  • From: Parks, Aaron B.
• Re: Intermitent slow queries
  • From: Parks, Aaron B.
• Re: Intermitent slow queries
  • From: Steinar H. Gunderson
• Re: Intermitent slow queries
  • From: Ron
• Re: Intermitent slow queries
  • From: Dave Cramer
• Intermitent slow queries
  • From: Parks, Aaron B.
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: david
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Greg Smith
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Greg Smith
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: david
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Carlos Moreno
• Re: index structure for 114-dimension vector
  • From: Alexander Staubo
• Re: index structure for 114-dimension vector
  • From: Andrew Lazarus
• Re: sytem log audit/reporting and psql
  • From: Andreas Haumer
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Josh Berkus
• Re: Query performance problems with partitioned tables
  • From: Gregory Stark
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Kevin Hunter
• Re: Query performance problems with partitioned tables
  • From: Steinar H. Gunderson
• Re: Query performance problems with partitioned tables
  • From: Andreas Haumer
• Re: Query performance problems with partitioned tables
  • From: Andreas Haumer
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Craig A. James
• Re: Query performance problems with partitioned tables
  • From: Gregory Stark
• Re: Query performance problems with partitioned tables
  • From: Tom Lane
• sytem log audit/reporting and psql
  • From: Fei Liu
• Re: Query performance problems with partitioned tables
  • From: Neil Peter Braggio
• Re: Query performance problems with partitioned tables
  • From: Guillaume Cottenceau
• Re: Query performance problems with partitioned tables
  • From: Richard Huxton
• Re: Query performance problems with partitioned tables
  • From: Andreas Haumer
• Re: Query performance problems with partitioned tables
  • From: Guillaume Cottenceau
• Query performance problems with partitioned tables
  • From: Andreas Haumer
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Greg Smith
• Re: Redundant sub query triggers slow nested loop left join
  • From: henk de wit
• Re: Very specific server situation
  • From: Mauro N. Infantino
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Carlos Moreno
• Re: Usage up to 50% CPU
  • From: Andres Retzlaff
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Harald Armin Massa
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Jonah H. Harris
• Re: Redundant sub query triggers slow nested loop left join
  • From: henk de wit
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Harald Armin Massa
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: david
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Josh Berkus
• Re: Very specific server situation
  • From: Tom Lane
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Dan Harris
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Josh Berkus
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Ray Stell
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Kevin Hunter
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Bill Moran
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Josh Berkus
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Dan Harris
• Very specific server situation
  • From: Mauro N. Infantino
• Re: How can fixed and variable width columns perform similarly?
  • From: Tom Lane
• Re: How can fixed and variable width columns perform similarly?
  • From: Siddharth Anand
• Re: How can fixed and variable width columns perform similarly?
  • From: Dave Dutcher
• Re: [Fwd: ] How
  • From: Richard Huxton
• Re: How can fixed and variable width columns perform similarly?
  • From: Tom Lane
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Jim Nasby
• How can fixed and variable width columns perform similarly?
  • From: Siddharth Anand
• [Fwd: ] How
  • From: Siddharth Anand
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Michael Stone
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: H.J. Sanders
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Mark Lewis
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Tom Lane
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Michael Stone
• Re: What`s wrong with JFS configuration?
  • From: Jim Nasby
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Carlos Moreno
• Re: Usage up to 50% CPU
  • From: Michael Stone
• Re: Usage up to 50% CPU
  • From: Shane Ambler
• Re: Usage up to 50% CPU
  • From: Magnus Hagander
• Re: Usage up to 50% CPU
  • From: Andres Retzlaff
• Re: Usage up to 50% CPU
  • From: Magnus Hagander
• Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
  • From: Florian Weimer
• Re: index structure for 114-dimension vector
  • From: Arjen van der Meijden
• Re: Fragmentation of WAL files
  • From: Greg Smith
• Re: Simple query, 10 million records...MySQL ten times faster
  • From: Oleg Bartunov
• Re: index structure for 114-dimension vector
  • From: Oleg Bartunov
• Usage up to 50% CPU
  • From: Andres Retzlaff
• Re: Feature Request --- was: PostgreSQL Performance Tuning
  • From: Tom Lane
• Feature Request --- was: PostgreSQL Performance Tuning
  • From: Carlos Moreno
• Re: Simple query, 10 million records...MySQL ten times faster
  • From: joe
• Re: postgres: 100% CPU utilization
  • From: Mark Kirkwood
• Re: Simple query, 10 million records...MySQL ten times faster
  • From: Alexander Staubo
• Re: Simple query, 10 million records...MySQL ten times faster
  • From: Alexander Staubo
• Re: postgres: 100% CPU utilization
  • From: Scott Marlowe
• Re: Simple query, 10 million records...MySQL ten times faster
  • From: Jeff Hoffmann
• Re: Simple query, 10 million records...MySQL ten times faster
  • From: Scott Marlowe
• Re: index structure for 114-dimension vector
  • From: Alexander Staubo
• Re: Simple query, 10 million records...MySQL ten times faster
  • From: Luke Lonergan
• Re: Simple query, 10 million records...MySQL ten times faster
  • From: Benjamin Minshall
• Re: Simple query, 10 million records...MySQL ten times faster
  • From: Bill Moran
• Re: Simple query, 10 million records...MySQL ten times faster
  • From: Merlin Moncure
• Re: [GENERAL] PostgreSQL Performance Tuning
  • From: Steve Crawford
• Re: not using indexes on large table
  • From: Scott Marlowe
• Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
  • From: Tom Lane
• Re: [GENERAL] Fw: PostgreSQL Performance Tuning
  • From: Gerhard Wiesinger
• Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
  • From: Gregory Stark
• Re: Filesystem fragmentation (Re: Fragmentation of WAL files)
  • From: Craig A. James
• Re: Fragmentation of WAL files
  • From: Tom Lane
• Filesystem fragmentation (Re: Fragmentation of WAL files)
  • From: Bill Moran
• Re: Fragmentation of WAL files
  • From: Heikki Linnakangas
• Re: Fragmentation of WAL files
  • From: Bill Moran
• Re: [GENERAL] Fw: PostgreSQL Performance Tuning
  • From: Richard Huxton
• Re: Fw: PostgreSQL Performance Tuning
  • From: Richard Huxton
• Fw: PostgreSQL Performance Tuning
  • From: Shohab Abdullah
• Re: What`s wrong with JFS configuration?
  • From: Cosimo Streppone
• Re: seeking advise on char vs text or varchar in search table
  • From: Gregory Stark
• Re: What`s wrong with JFS configuration?
  • From: Luke Lonergan
• Re: What`s wrong with JFS configuration?
  • From: Jim Nasby
• Re: seeking advise on char vs text or varchar in search table
  • From: Jim Nasby
• Fragmentation of WAL files
  • From: Jim Nasby
• Re: What`s wrong with JFS configuration?
  • From: Greg Smith
• Re: What`s wrong with JFS configuration?
  • From: Chris Browne
• Re: What`s wrong with JFS configuration?
  • From: Paweł Gruszczyński
• Re: What`s wrong with JFS configuration?
  • From: Dave Cramer
• Re: What`s wrong with JFS configuration?
  • From: Heikki Linnakangas
• What`s wrong with JFS configuration?
  • From: Paweł Gruszczyński
• Simple query, 10 million records...MySQL ten times faster
  • From: zardozrocks
• Re: View is not using a table index
  • From: Carlos Moreno
• Re: View is not using a table index
  • From: Tom Lane
• Re: View is not using a table index
  • From: Andreas Kostyrka
• Re: View is not using a table index
  • From: Dan Shea
• Re: View is not using a table index
  • From: Richard Huxton
• Re: postgres: 100% CPU utilization
  • From: Sergey Tsukinovsky
• View is not using a table index
  • From: Dan Shea
• Re: Warm - standby system.
  • From: Alexander Staubo
• Re: TPC-H Scaling Factors X PostgreSQL Cluster Command
  • From: Heikki Linnakangas
• Warm - standby system.
  • From: Nimesh Satam
• Re: postgres: 100% CPU utilization
  • From: Greg Smith
• Re: TPC-H Scaling Factors X PostgreSQL Cluster Command
  • From: Greg Smith
• Re: postgres: 100% CPU utilization
  • From: Mark Kirkwood
• Re: postgres: 100% CPU utilization
  • From: Scott Marlowe
• Re: postgres: 100% CPU utilization
  • From: Vivek Khera
• Re: TPC-H Scaling Factors X PostgreSQL Cluster Command
  • From: Kevin Grittner
• Re: index usage
  • From: Steinar H. Gunderson
• Re: index structure for 114-dimension vector
  • From: C Storm
• index usage
  • From: Arkadiusz Raj
• Re: postgres: 100% CPU utilization
  • From: Scott Marlowe
• Re: TPC-H Scaling Factors X PostgreSQL Cluster Command
  • From: Nelson Kotowski
• Re: postgres: 100% CPU utilization
  • From: Ron
• Re: not using indexes on large table
  • From: Dave Dutcher
• Re: Redundant sub query triggers slow nested loop left join
  • From: henk de wit
• Re: TPC-H Scaling Factors X PostgreSQL Cluster Command
  • From: Heikki Linnakangas
• Re: postgres: 100% CPU utilization
  • From: Mario Weilguni
• Re: Help with TOAST Compression
  • From: Michael Fuhr
• Re: postgres: 100% CPU utilization
  • From: Andreas Tille
• Re: seeking advise on char vs text or varchar in search table
  • From: Merlin Moncure
• Re: postgres: 100% CPU utilization
  • From: Tom Lane
• Re: Redundant sub query triggers slow nested loop left join
  • From: Tom Lane
• Re: Redundant sub query triggers slow nested loop left join
  • From: henk de wit
• Re: Redundant sub query triggers slow nested loop left join
  • From: henk de wit
• Re: Redundant sub query triggers slow nested loop left join
  • From: Tom Lane
• Re: Redundant sub query triggers slow nested loop left join
  • From: henk de wit
• Re: Redundant sub query triggers slow nested loop left join
  • From: Tom Lane
• Re: Redundant sub query triggers slow nested loop left join
  • From: henk de wit
• Re: Large objetcs performance
  • From: Ulrich Cech
• Re: Odd problem with planner choosing seq scan
  • From: Tom Lane
• Re: Odd problem with planner choosing seq scan
  • From: Colin McGuigan
• Re: Redundant sub query triggers slow nested loop left join
  • From: Tom Lane
• Redundant sub query triggers slow nested loop left join
  • From: henk de wit
• Re: not using indexes on large table
  • From: Andreas Kostyrka
• Re: not using indexes on large table
  • From: Vincenzo Romano
• not using indexes on large table
  • From: Jeroen Kleijer
• Re: Odd problem with planner choosing seq scan
  • From: Tom Lane
• Re: FK triggers misused?
  • From: Stephan Szabo
• Odd problem with planner choosing seq scan
  • From: Colin McGuigan
• TPC-H Scaling Factors X PostgreSQL Cluster Command
  • From: Nelson Kotowski
• Re: FK triggers misused?
  • From: cluster
• Re: Large objetcs performance
  • From: Ulrich Cech
• Odd problem with planner choosing seq scan
  • From: Colin McGuigan
• Re: index structure for 114-dimension vector
  • From: Tom Lane
• Re: index structure for 114-dimension vector
  • From: Mark Kirkwood
• Re: index structure for 114-dimension vector
  • From: Andrew Lazarus
• Re: index structure for 114-dimension vector
  • From: Mark Kirkwood
• Re: index structure for 114-dimension vector
  • From: Jeff Davis
• index structure for 114-dimension vector
  • From: Andrew Lazarus
• seeking advise on char vs text or varchar in search table
  • From: chrisj
• postgres: 100% CPU utilization
  • From: Sergey Tsukinovsky
• Re: how to output column names
  • From: Michael Dengler
• Re: how to output column names
  • From: Jon Sime
• how to output column names
  • From: Michael Dengler
• Re: Foreign Key Deadlocking
  • From: Csaba Nagy
• Re: Foreign Key Deadlocking
  • From: Alvaro Herrera
• Re: Foreign Key Deadlocking
  • From: Erik Jones
• Re: Foreign Key Deadlocking
  • From: Dave Cramer
• Re: Basic Q on superfluous primary keys
  • From: Merlin Moncure
• Re: Foreign Key Deadlocking
  • From: Steven Flatt
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Hannes Dorbath
• Re: Basic Q on superfluous primary keys
  • From: Jeff Davis
• Re: Long running transactions again ...
  • From: Jim C. Nasby
• Re: Basic Q on superfluous primary keys
  • From: Dave Dutcher
• Re: a question about Direct I/O and double buffering
  • From: Jim C. Nasby
• Re: Foreign Key Deadlocking
  • From: Tom Lane
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Jim C. Nasby
• Re: Basic Q on superfluous primary keys
  • From: Craig A. James
• Re: Foreign Key Deadlocking
  • From: Csaba Nagy
• Foreign Key Deadlocking
  • From: Steven Flatt
• Re: Basic Q on superfluous primary keys
  • From: Merlin Moncure
• Re: Basic Q on superfluous primary keys
  • From: Greg Smith
• Re: Basic Q on superfluous primary keys
  • From: Richard Huxton
• Re: Basic Q on superfluous primary keys
  • From: Craig A. James
• Re: Basic Q on superfluous primary keys
  • From: Craig A. James
• Help with TOAST Compression
  • From: David Hinkle
• Re: FK triggers misused?
  • From: cluster
• Re: Basic Q on superfluous primary keys
  • From: Merlin Moncure
• Re: Fwd: Strangely Variable Query Performance
  • From: Tom Lane
• Fwd: Strangely Variable Query Performance
  • From: Robins
• Fwd: Strangely Variable Query Performance
  • From: Robins Tharakan
• Re: Basic Q on superfluous primary keys
  • From: Greg Smith
• Re: FK triggers misused?
  • From: Tom Lane
• Re: FK triggers misused?
  • From: Tom Lane
• Re: FK triggers misused?
  • From: cluster
• Re: Basic Q on superfluous primary keys
  • From: Ron Mayer
• Re: Basic Q on superfluous primary keys
  • From: Merlin Moncure
• Re: Basic Q on superfluous primary keys
  • From: Craig A. James
• Re: Basic Q on superfluous primary keys
  • From: Merlin Moncure
• Re: FK triggers misused?
  • From: Andrew - Supernews
• Re: FK triggers misused?
  • From: Tom Lane
• Re: FK triggers misused?
  • From: Andrew - Supernews
• Re: FK triggers misused?
  • From: Tom Lane
• Re: [HACKERS] choose_bitmap_and again (was Re: Strangely Variable Query Performance)
  • From: Tom Lane
• Re: [HACKERS] choose_bitmap_and again (was Re: Strangely Variable Query Performance)
  • From: Tom Lane
• Re: Question about memory allocations
  • From: Tom Lane
• Re: [HACKERS] choose_bitmap_and again (was Re: Strangely Variable Query Performance)
  • From: Tom Lane
• FK triggers misused?
  • From: cluster
• Re: Basic Q on superfluous primary keys
  • From: Bill Moran
• Basic Q on superfluous primary keys
  • From: Kynn Jones
• Re: Finding bloated indexes?
  • From: Simon Riggs
• Re: [HACKERS] choose_bitmap_and again (was Re: Strangely Variable Query Performance)
  • From: Alvaro Herrera
• choose_bitmap_and again (was Re: Strangely Variable Query Performance)
  • From: Tom Lane
• Re: Finding bloated indexes?
  • From: Vivek Khera
• Re: Please humor me ...
  • From: Simon Riggs
• Re: Question about memory allocations
  • From: Jan de Visser
• Finding bloated indexes?
  • From: Dan Harris
• Re: Question about memory allocations
  • From: Carlos Moreno
• Re: Question about memory allocations
  • From: Ron
• Re: Question about memory allocations
  • From: Steve
• Re: local selectivity estimation - computing frequency of predicates
  • From: Tom Lane
• local selectivity estimation - computing frequency of predicates
  • From: Avdhoot Kishore Saple
• Re: Question about memory allocations
  • From: Andrew McMillan
• Re: Strangely Variable Query Performance
  • From: Tom Lane
• Re: Question about memory allocations
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Tom Lane
• Re: Question about memory allocations
  • From: Greg Smith
• Re: Strangely Variable Query Performance
  • From: Tom Lane
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Tom Lane
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Tom Lane
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Tom Lane
• Re: Strangely Variable Query Performance
  • From: Tom Lane
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Tom Lane
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Tom Lane
• Re: Slow Postgresql server
  • From: Guido Neitzer
• Re: Strangely Variable Query Performance
  • From: Scott Marlowe
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Tom Lane
• Re: Slow Postgresql server
  • From: Jason Lustig
• Re: Strangely Variable Query Performance
  • From: Scott Marlowe
• Re: Strangely Variable Query Performance
  • From: Steve
• Re: Strangely Variable Query Performance
  • From: Tom Lane
• Strangely Variable Query Performance
  • From: Steve
• Re: Slow Postgresql server
  • From: Carlos Moreno
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Robert Treat
• Re: Slow Postgresql server
  • From: Jeff Frost
• Re: Slow Postgresql server
  • From: Scott Marlowe
• Re: Question about memory allocations
  • From: Steve
• Re: Slow Postgresql server
  • From: Jeff Frost
• Re: Slow Postgresql server
  • From: Guido Neitzer
• Re: Slow Postgresql server
  • From: Ron
• Re: Slow Postgresql server
  • From: Guido Neitzer
• Re: Large objetcs performance
  • From: Merlin Moncure
• Re: Slow Postgresql server
  • From: Ron
• Re: Slow Postgresql server
  • From: Jeff Frost
• Re: Slow Postgresql server
  • From: Dennis Bjorklund
• Re: Question about memory allocations
  • From: Tom Lane
• Slow Postgresql server
  • From: Jason Lustig
• Question about memory allocations
  • From: Steve
• Re: Beginner Question
  • From: Jan de Visser
• Re: Do I need to rebuild php-pgsql for 8.2.3
  • From: Michael Dengler
• Re: Do I need to rebuild php-pgsql for 8.2.3
  • From: Devrim GÜNDÜZ
• Re: Do I need to rebuild php-pgsql for 8.2.3
  • From: Adam Rich
• Re: Do I need to rebuild php-pgsql for 8.2.3
  • From: Michael Dengler
• Long running transactions again ...
  • From: Tobias Brox
• Re: Do I need to rebuild php-pgsql for 8.2.3
  • From: Devrim GÜNDÜZ
• Re: Do I need to rebuild php-pgsql for 8.2.3
  • From: Guillaume Smet
• Do I need to rebuild php-pgsql for 8.2.3
  • From: Michael Dengler
• Re: join to view over custom aggregate seems like it should be faster
  • From: Tom Lane
• Re: join to view over custom aggregate seems like it should be faster
  • From: Merlin Moncure
• Re: join to view over custom aggregate seems like it should be faster
  • From: Tom Lane
• Re: DELETE with filter on ctid
  • From: Tom Lane
• Re: how to efficiently update tuple in many-to-many relationship?
  • From: Tom Lane
• Re: how to efficiently update tuple in many-to-many relationship?
  • From: Drew Wilson
• Re: Beginner Question
  • From: Dave Dutcher
• Re: how to efficiently update tuple in many-to-many relationship?
  • From: Tom Lane
• Re: DELETE with filter on ctid
  • From: Spiegelberg, Greg
• Re: DELETE with filter on ctid
  • From: Spiegelberg, Greg
• Re: Beginner Question
  • From: Mike Gargano
• Re: join to view over custom aggregate seems like it should be faster
  • From: Merlin Moncure
• Re: how to efficiently update tuple in many-to-many relationship?
  • From: Drew Wilson
• Re: how to efficiently update tuple in many-to-many relationship?
  • From: Tom Lane
• Re: how to efficiently update tuple in many-to-many relationship?
  • From: Drew Wilson
• Re: Beginner Question
  • From: s d
• Re: DELETE with filter on ctid
  • From: Craig A. James
• Re: how to efficiently update tuple in many-to-many relationship?
  • From: Tom Lane
• Re: join to view over custom aggregate seems like it should be faster
  • From: Merlin Moncure
• Re: join to view over custom aggregate seems like it should be faster
  • From: Merlin Moncure
• Re: how to efficiently update tuple in many-to-many relationship?
  • From: Merlin Moncure
• Re: join to view over custom aggregate seems like it should be faster
  • From: Tom Lane
• Re: Please humor me ...
  • From: Jeff Davis
• Re: DELETE with filter on ctid
  • From: Tom Lane
• how to efficiently update tuple in many-to-many relationship?
  • From: Drew Wilson
• Re: postgres 8.2 seems to prefer Seq Scan
  • From: Alex Deucher
• Please humor me ...
  • From: Carlos Moreno
• DELETE with filter on ctid
  • From: Spiegelberg, Greg
• Re: postgres 8.2 seems to prefer Seq Scan
  • From: Alex Deucher
• join to view over custom aggregate seems like it should be faster
  • From: Merlin Moncure
• Re: postgres 8.2 seems to prefer Seq Scan
  • From: Alex Deucher
• Re: Beginner Question
  • From: Tom Lane
• Beginner Question
  • From: s d
• Re: SCSI vs SATA
  • From: James Mansion
• Re: SCSI vs SATA
  • From: Ron
• Re: SCSI vs SATA
  • From: mark
• Re: SCSI vs SATA
  • From: Joshua D. Drake
• Re: SCSI vs SATA
  • From: david
• Re: SCSI vs SATA
  • From: Ron
• Re: SCSI vs SATA
  • From: david
• Re: fast DISTINCT or EXIST
  • From: Arjen van der Meijden
• Re: fast DISTINCT or EXIST
  • From: Tom Lane
• Re: fast DISTINCT or EXIST
  • From: Tilo Buschmann
• Re: fast DISTINCT or EXIST
  • From: Tom Lane
• Re: SCSI vs SATA
  • From: Ron
• Re: fast DISTINCT or EXIST
  • From: Arjen van der Meijden
• fast DISTINCT or EXIST
  • From: Tilo Buschmann
• Re: SCSI vs SATA
  • From: Bruce Momjian
• Re: SCSI vs SATA
  • From: Mark Kirkwood
• Re: SCSI vs SATA
  • From: Andreas Kostyrka
• Re: SCSI vs SATA
  • From: david
• Re: SCSI vs SATA
  • From: Charles Sprickman
• Re: SCSI vs SATA
  • From: david
• Re: postgres 8.2 seems to prefer Seq Scan
  • From: Alex Deucher
• Re: postgres 8.2 seems to prefer Seq Scan
  • From: Michael Fuhr
• Re: SCSI vs SATA
  • From: Michael Stone
• Re: SCSI vs SATA
  • From: Greg Smith
• postgres 8.2 seems to prefer Seq Scan
  • From: Alex Deucher
• Re: Premature view materialization in 8.2?
  • From: Jonathan Ellis
• Re: SCSI vs SATA
  • From: Ron
• Re: Premature view materialization in 8.2?
  • From: Tom Lane
• Re: SCSI vs SATA
  • From: Michael Stone
• Re: Premature view materialization in 8.2?
  • From: Jonathan Ellis
• Re: Premature view materialization in 8.2?
  • From: Tom Lane
• Re: Premature view materialization in 8.2?
  • From: Jonathan Ellis
• Re: Premature view materialization in 8.2?
  • From: Tom Lane
• Re: more on high load on postgres 7.4.16
  • From: Geoffrey
• Re: SCSI vs SATA
  • From: Ron
• Re: more on high load on postgres 7.4.16
  • From: Stefan Kaltenbrunner
• more on high load on postgres 7.4.16
  • From: Geoffrey
• Re: High Load on Postgres 7.4.16 Server
  • From: John Allgood
• Re: SCSI vs SATA
  • From: Scott Marlowe
• Re: Premature view materialization in 8.2?
  • From: Jonathan Ellis
• Re: SCSI vs SATA
  • From: Michael Stone
• Re: SCSI vs SATA
  • From: Geoffrey
• Re: SCSI vs SATA
  • From: Ron
• Re: SCSI vs SATA
  • From: Geoffrey
• Re: SCSI vs SATA
  • From: Ron
• Re: SCSI vs SATA
  • From: Michael Stone
• Re: SCSI vs SATA
  • From: Michael Stone
• Re: SCSI vs SATA
  • From: Tom Lane
• Re: Premature view materialization in 8.2?
  • From: Tom Lane
• Re: SCSI vs SATA
  • From: Greg Smith
• Re: SCSI vs SATA
  • From: Tom Lane
• Re: Premature view materialization in 8.2?
  • From: Jonathan Ellis
• Re: High Load on Postgres 7.4.16 Server
  • From: Tom Lane
• Re: SCSI vs SATA
  • From: david
• Re: Premature view materialization in 8.2?
  • From: Tom Lane
• Re: SCSI vs SATA
  • From: Ron
• Re: SCSI vs SATA
  • From: Greg Smith
• Re: SCSI vs SATA
  • From: Richard Troy
• Re: a question about Direct I/O and double buffering
  • From: david
• Re: SCSI vs SATA
  • From: david
• Re: SCSI vs SATA
  • From: Ron
• Re: SCSI vs SATA
  • From: david
• Re: a question about Direct I/O and double buffering
  • From: david
• Re: Weird performance drop
  • From: Vincenzo Romano
• Re: a question about Direct I/O and double buffering
  • From: Erik Jones
• Re: SCSI vs SATA
  • From: Scott Marlowe
• Re: a question about Direct I/O and double buffering
  • From: Alex Deucher
• Re: a question about Direct I/O and double buffering
  • From: Xiaoning Ding
• Re: a question about Direct I/O and double buffering
  • From: david
• Re: High Load on Postgres 7.4.16 Server
  • From: Dave Cramer
• Re: High Load on Postgres 7.4.16 Server
  • From: John Allgood
• Re: a question about Direct I/O and double buffering
  • From: Erik Jones
• Re: SCSI vs SATA
  • From: david
• Re: SCSI vs SATA
  • From: david
• Re: High Load on Postgres 7.4.16 Server
  • From: Dave Cramer
• Re: a question about Direct I/O and double buffering
  • From: Mark Lewis
• Re: High Load on Postgres 7.4.16 Server
  • From: Jeff Frost
• Re: High Load on Postgres 7.4.16 Server
  • From: John Allgood
• Re: SCSI vs SATA
  • From: James Mansion
• Re: High Load on Postgres 7.4.16 Server
  • From: "C. Bergström"
• Re: High Load on Postgres 7.4.16 Server
  • From: Jeff Frost
• High Load on Postgres 7.4.16 Server
  • From: John Allgood
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Dimitri
• Re: a question about Direct I/O and double buffering
  • From: Erik Jones
• Re: a question about Direct I/O and double buffering
  • From: Alex Deucher
• Re: a question about Direct I/O and double buffering
  • From: Erik Jones
• Premature view materialization in 8.2?
  • From: Jonathan Ellis
• Re: a question about Direct I/O and double buffering
  • From: Mark Lewis
• Re: a question about Direct I/O and double buffering
  • From: Xiaoning Ding
• Re: a question about Direct I/O and double buffering
  • From: Erik Jones
• Re: What do the adminpack functions do? (8.2.3)
  • From: Joshua D. Drake
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Josh Berkus
• What do the adminpack functions do? (8.2.3)
  • From: Michael Dengler
• a question about Direct I/O and double buffering
  • From: Xiaoning Ding
• Re: SCSI vs SATA
  • From: Arjen van der Meijden
• Re: SCSI vs SATA
  • From: Ron
• Re: SCSI vs SATA
  • From: Alex Deucher
• Re: SCSI vs SATA
  • From: Joshua D. Drake
• Re: SCSI vs SATA
  • From: jason@xxxxxxxxx
• Re: SCSI vs SATA
  • From: jason@xxxxxxxxx
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Alex Deucher
• Re: SCSI vs SATA
  • From: Jeff Frost
• Re: SCSI vs SATA
  • From: Scott Marlowe
• Re: SCSI vs SATA
  • From: Scott Marlowe
• Re: SCSI vs SATA
  • From: Ron
• Re: SCSI vs SATA
  • From: Heikki Linnakangas
• Re: SCSI vs SATA
  • From: Arjen van der Meijden
• Re: SCSI vs SATA
  • From: Tom Lane
• Re: SCSI vs SATA
  • From: James Mansion
• [no subject]
  • From: Unknown
• [no subject]
  • From: Unknown
• Re: SCSI vs SATA
  • From: jason@xxxxxxxxx
• Re: SCSI vs SATA
  • From: Carlos Moreno
• Re: SCSI vs SATA
  • From: Bruce Momjian
• Re: SCSI vs SATA
  • From: Joshua D. Drake
• Re: SCSI vs SATA
  • From: Bruce Momjian
• Re: SCSI vs SATA
  • From: Arjen van der Meijden
• Re: SCSI vs SATA
  • From: jason@xxxxxxxxx
• Re: SCSI vs SATA
  • From: Arjen van der Meijden
• Re: SCSI vs SATA
  • From: James Mansion
• Re: SCSI vs SATA
  • From: Geoff Tolley
• Re: SCSI vs SATA
  • From: Geoff Tolley
• Re: Scaling SELECT:s with the number of disks on a stripe
  • From: Peter Schuller
• Re: SCSI vs SATA
  • From: Geoff Tolley
• Re: SCSI vs SATA
  • From: mark
• Re: Can't drop tablespace or user after disk gone
  • From: Tom Lane
• Can't drop tablespace or user after disk gone
  • From: Craig A. James
• Re: SCSI vs SATA
  • From: Stefan Kaltenbrunner
• Re: SCSI vs SATA
  • From: david
• Re: SCSI vs SATA
  • From: Joshua D. Drake
• Re: SCSI vs SATA
  • From: Andreas Kostyrka
• Re: SCSI vs SATA
  • From: Joshua D. Drake
• Re: SCSI vs SATA
  • From: Stefan Kaltenbrunner
• Re: SCSI vs SATA
  • From: Joshua D. Drake
• Re: SCSI vs SATA
  • From: Ron
• Re: SCSI vs SATA
  • From: jason@xxxxxxxxx
• Re: Large objetcs performance
  • From: Guido Neitzer
• Large objetcs performance
  • From: Alexandre Vasconcelos
• Re: SCSI vs SATA
  • From: Andreas Kostyrka
• Re: SCSI vs SATA
  • From: Rod Taylor
• Re: SCSI vs SATA
  • From: Alvaro Herrera
• Re: SCSI vs SATA
  • From: Peter Kovacs
• Re: SCSI vs SATA
  • From: Alvaro Herrera
• Re: SCSI vs SATA
  • From: Andreas Kostyrka
• Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Dimitri
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Arnau
• Re: Scaling SELECT:s with the number of disks on a stripe
  • From: Andrew - Supernews
• Re: Scaling SELECT:s with the number of disks on a stripe
  • From: Dave Cramer
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Arnau
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Ansgar -59cobalt- Wiechers
• Re: SCSI vs SATA
  • From: Peter Kovacs
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Arnau
• Re: SCSI vs SATA
  • From: Ron Mayer
• postgresql.conf file for PostgreSQL 8.2.3
  • From: Eugene Ogurtsov
• Re: Scaling SELECT:s with the number of disks on a stripe
  • From: Peter Schuller
• Re: compact flash disks?
  • From: James Mansion
• Re: SCSI vs SATA
  • From: david
• Re: SCSI vs SATA
  • From: Brian A. Seklecki
• Re: SCSI vs SATA
  • From: Geoff Tolley
• Re: SCSI vs SATA
  • From: Ron
• Re: SCSI vs SATA
  • From: Ron
• SCSI vs SATA
  • From: jason@xxxxxxxxx
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Alex Deucher
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Alex Deucher
• Re: [HACKERS] EXISTS optimization
  • From: Craig A. James
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Alex Deucher
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Tom Lane
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Alex Deucher
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Alex Deucher
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Alex Deucher
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Merlin Moncure
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: A.M.
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Alan Hodgson
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: A.M.
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: "C. Bergström"
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Alex Deucher
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Erik Jones
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: A.M.
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Tom Lane
• Re: Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Josh Berkus
• Equivalents in PostgreSQL of MySQL's "ENGINE=MEMORY" "MAX_ROWS=1000"
  • From: Arnau
• Re: Cache hit ratio
  • From: Josh Berkus
• Re: Cache hit ratio
  • From: Ben
• Re: Cache hit ratio
  • From: Luke Lonergan
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Dimitri
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Alex Deucher
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Josh Berkus
• Re: Cache hit ratio
  • From: Guillaume Cottenceau
• Cache hit ratio
  • From: Jean Arnaud
• Re: postgres 7.4 vs 8.x redux: query plans
  • From: Tom Lane
• postgres 7.4 vs 8.x redux: query plans
  • From: Alex Deucher
• Re: Scaling SELECT:s with the number of disks on a stripe
  • From: Andrew - Supernews
• postgres 7.4 vs. 8.x redux
  • From: Alex Deucher
• Re: Providing user based previleges to Postgres DB
  • From: Carlos Moreno
• Providing user based previleges to Postgres DB
  • From: ramachandra.bhaskaram
• Re: Scaling SELECT:s with the number of disks on a stripe
  • From: Peter Schuller
• Re: Wrong plan sequential scan instead of an index one [8.2 solved it]
  • From: Gaetano Mendola
• Re: Scaling SELECT:s with the number of disks on a stripe
  • From: Peter Schuller
• Re: How to determine which indexes are not using or using seldom in database
  • From: Andreas Kostyrka
• Re: How to determine which indexes are not using or using seldom in database
  • From: Thomas Pundt
• How to determine which indexes are not using or using seldom in database
  • From: Denis Lishtovny
• Re: scalablility problem
  • From: Dave Cramer
• Re: scalablility problem
  • From: Xiaoning Ding
• Re: scalablility problem
  • From: Ron Mayer
• Re: Scaling SELECT:s with the number of disks on a stripe
  • From: Andrew - Supernews
• Re: scalablility problem
  • From: Xiaoning Ding
• Re: scalablility problem
  • From: Tom Lane
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Erik Jones
• Re: scalablility problem
  • From: Xiaoning Ding
• Re: scalablility problem
  • From: Xiaoning Ding
• Re: scalablility problem
  • From: Joshua D. Drake
• Re: scalablility problem
  • From: Xiaoning Ding
• Re: scalablility problem
  • From: Michael Stone
• Re: scalablility problem
  • From: Guido Neitzer
• Re: scalablility problem
  • From: Christopher Browne
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Josh Berkus
• Re: scalablility problem
  • From: Scott Marlowe
• Re: scalablility problem
  • From: Scott Marlowe
• Re: scalablility problem
  • From: Xiaoning Ding
• Re: scalablility problem
  • From: Tom Lane
• Re: scalablility problem
  • From: Dave Dutcher
• scalablility problem
  • From: Xiaoning Ding
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Erik Jones
• Re: Wrong plan sequential scan instead of an index one
  • From: Tom Lane
• Re: Weird performance drop
  • From: Dave Dutcher
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Dimitri
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Erik Jones
• Re: Wrong plan sequential scan instead of an index one
  • From: Matteo Beccati
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Dimitri
• Re: Wrong plan sequential scan instead of an index one
  • From: Richard Huxton
• Re: Wrong plan sequential scan instead of an index one
  • From: Gaetano Mendola
• Re: Wrong plan sequential scan instead of an index one
  • From: Gaetano Mendola
• Re: Wrong plan sequential scan instead of an index one
  • From: Michael Fuhr
• Re: Wrong plan sequential scan instead of an index one
  • From: Michael Fuhr
• Re: Wrong plan sequential scan instead of an index one
  • From: ismo . tuononen
• Re: Wrong plan sequential scan instead of an index one
  • From: Richard Huxton
• Re: Wrong plan sequential scan instead of an index one
  • From: Gaetano Mendola
• Re: Wrong plan sequential scan instead of an index one
  • From: Gaetano Mendola
• Re: Wrong plan sequential scan instead of an index one
  • From: Richard Huxton
• Re: Wrong plan sequential scan instead of an index one
  • From: Claus Guttesen
• Wrong plan sequential scan instead of an index one
  • From: Gaetano Mendola
• Re: Planner doing seqscan before indexed join
  • From: Marc Mamin
• Re: Scaling SELECT:s with the number of disks on a stripe
  • From: Marc Mamin
• Re: Weird performance drop
  • From: Vincenzo Romano
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Erik Jones
• Scaling SELECT:s with the number of disks on a stripe
  • From: Peter Schuller
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Greg Smith
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Erik Jones
• Re: Sunfire X4500 recommendations
  • From: david
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Josh Berkus
• Re: Planner doing seqscan before indexed join
  • From: Dave Dutcher
• Re: Weird performance drop
  • From: Dave Dutcher
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Dimitri
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Erik Jones
• Re: Shared buffers, db transactions commited, and write IO on Solaris
  • From: Tom Lane