• Text Size: Normal / Large
• Donate
• Contact

Section Navigation

• Community
• Mailing Lists
  • Subscribe
  • User lists
    • pgsql-admin
    • pgsql-advocacy
    • pgsql-announce
    • pgsql-bugs
    • pgsql-docs
    • pgsql-cygwin
    • pgsql-general
    • pgsql-interfaces
    • pgsql-jdbc
    • pgsql-jobs
    • pgsql-novice
    • pgsql-odbc
    • pgsql -performance
    • pgsql-php
    • pgsql-ports
    • pgsql-sql
  • Developer lists
  • Regional lists
  • Project lists
  • User groups
  • Inactive lists
• IRC
• In The Real World
• International Sites
• Propaganda
• Resources
• Weekly News

pgsql-performance 2006-03 Chronological Index (1/4)

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

• 28 March 2008
  • [no subject] Unknown
  • [no subject] Unknown
  • [no subject] Unknown
• 01 April 2006
  • Re: Query using SeqScan instead of IndexScan Brendan Duddridge
  • Re: Query using SeqScan instead of IndexScan chris smith
  • Re: Query using SeqScan instead of IndexScan Brendan Duddridge
• 31 March 2006
  • Re: [Solved] Slow performance on Windows .NET and OleDb Magnus Hagander
  • Re: [Solved] Slow performance on Windows .NET and OleDb Antoine
  • Re: un-'vacuum analyse' Tom Lane
  • un-'vacuum analyse' Frederic Back
  • Re: Query using SeqScan instead of IndexScan Jim C. Nasby
  • Re: Indexes with descending date columns Jim C. Nasby
  • Re: simple join uses indexes, very slow Jim C. Nasby
  • Re: index not used again Stephan Szabo
  • index not used again Jan Kesten
  • Re: Decide between Postgresql and Mysql (help of Guido Neitzer
  • Re: Decide between Postgresql and Mysql (help of Philippe Marzin
• 30 March 2006
  • Re: Decide between Postgresql and Mysql (help of Chris Browne
  • Re: Decide between Postgresql and Mysql (help of Steinar H. Gunderson
  • Re: Decide between Postgresql and Mysql (help of PFC
  • Re: CREATE INDEX rather sluggish Gavin Hamill
  • Re: CREATE INDEX rather sluggish Gavin Hamill
  • Re: Decide between Postgresql and Mysql (help of Scott Marlowe
  • Re: Decide between Postgresql and Mysql (help of Chris Browne
  • Re: Index scan startup time Simon Riggs
  • Re: CREATE INDEX rather sluggish Simon Riggs
  • Re: Index scan startup time Tom Lane
  • Re: CREATE INDEX rather sluggish Tom Lane
  • Re: Index scan startup time Peter Eisentraut
  • Re: [Solved] Slow performance on Windows .NET and OleDb Dave Dutcher
  • Re: Index scan startup time Tom Lane
  • Automatic tuning of postgresql.conf parameters? Mattias Kregert
  • Re: Index scan startup time Michael Stone
  • Re: Index scan startup time Steinar H. Gunderson
  • Re: Index scan startup time Peter Eisentraut
  • Re: Index scan startup time Steinar H. Gunderson
  • Re: Index scan startup time Michael Stone
  • Re: Index scan startup time Markus Schaber
  • Re: Index scan startup time Steinar H. Gunderson
  • Re: Index scan startup time Peter Eisentraut
  • Re: Index scan startup time Peter Eisentraut
  • Re: Index scan startup time Michael Stone
  • Re: Index scan startup time Steinar H. Gunderson
  • Index scan startup time Peter Eisentraut
  • Re: Decide between Postgresql and Mysql (help of Markus Schaber
  • CREATE INDEX rather sluggish Gavin Hamill
  • [Solved] Slow performance on Windows .NET and OleDb Greg Quinn
  • Re: Query using SeqScan instead of IndexScan Josh Berkus
  • Re: Database possible corruption , unsolvable mystery Josh Berkus
  • Re: Query using SeqScan instead of IndexScan Brendan Duddridge
  • Query using SeqScan instead of IndexScan Brendan Duddridge
  • Re: Decide between Postgresql and Mysql (help of Gorshkov
  • Re: Decide between Postgresql and Mysql (help of Craig A. James
  • Re: Decide between Postgresql and Mysql (help of Gorshkov
  • Re: Decide between Postgresql and Mysql (help of Craig A. James
  • Re: Slow performance on Windows .NET and OleDb Christopher Kings-Lynne
  • Re: Decide between Postgresql and Mysql (help of Gorshkov
• 29 March 2006
  • Re: Database possible corruption , unsolvable mystery Eric Lauzon
  • Re: Database possible corruption , unsolvable mystery stef
  • Re: Database possible corruption , unsolvable mystery Eric Lauzon
  • Re: Database possible corruption , unsolvable mystery Mark Lewis
  • Re: Database possible corruption , unsolvable mystery Richard Huxton
  • Database possible corruption , unsolvable mystery Eric Lauzon
  • Re: Decide between Postgresql and Mysql (help of Vivek Khera
  • Re: Decide between Postgresql and Mysql (help of Vivek Khera
  • Re: Decide between Postgresql and Mysql (help of comunity) Vivek Khera
  • Re: simple join uses indexes, very slow george young
  • Re: Slow performance on Windows .NET and OleDb Merlin Moncure
  • Re: Decide between Postgresql and Mysql (help of Merlin Moncure
  • statistics buffer is full Gábriel Ákos
  • Re: Slow performance on Windows .NET and OleDb PFC
  • Re: Slow performance on Windows .NET and OleDb Markus Schaber
  • Re: Slow performance on Windows .NET and OleDb Greg Quinn
  • Re: Indexes with descending date columns Theo Kramer
  • Re: Slow performance on Windows .NET and OleDb Chris
  • Re: Slow performance on Windows .NET and OleDb Ruben Rubio Rey
  • Re: Slow performance on Windows .NET and OleDb Greg Quinn
  • Re: Slow performance on Windows .NET and OleDb Greg Quinn
  • Re: simple join uses indexes, very slow stef
  • Re: simple join uses indexes, very slow Chris
  • Re: MVCC intro and benefits docs? Qingqing Zhou
  • Re: simple join uses indexes, very slow Dave Dutcher
• 28 March 2006
  • Re: MVCC intro and benefits docs? Jim C. Nasby
  • Re: Decide between Postgresql and Mysql (help of Jim C. Nasby
  • Re: Decide between Postgresql and Mysql (help of Jim C. Nasby
  • Re: Decide between Postgresql and Mysql (help of PFC
  • Re: Decide between Postgresql and Mysql (help of PFC
  • Re: simple join uses indexes, very slow george young
  • Re: Decide between Postgresql and Mysql (help of Chris Travers
  • Re: Decide between Postgresql and Mysql (help of Scott Marlowe
  • Re: Decide between Postgresql and Mysql (help of PFC
  • Re: Decide between Postgresql and Mysql (help of Marcos
  • MVCC intro and benefits docs? Antoine
  • Re: Decide between Postgresql and Mysql (help of Scott Marlowe
  • Re: Decide between Postgresql and Mysql (help of comunity) Madison Kelly
  • Decide between Postgresql and Mysql (help of comunity) Marcos
  • Re: simple join uses indexes, very slow Simon Riggs
  • Re: Slow performance on Windows .NET and OleDb Joshua D. Drake
  • Re: Massive Inserts Strategies Jim C. Nasby
  • Re: simple join uses indexes, very slow Steinar H. Gunderson
  • Re: Slow performance on Windows .NET and OleDb Jim C. Nasby
  • Re: simple join uses indexes, very slow Jim C. Nasby
  • Re: count(*) performance Jim C. Nasby
  • Re: simple join uses indexes, very slow Dave Dutcher
  • Re: simple join uses indexes, very slow Steinar H. Gunderson
  • Re: Massive Inserts Strategies Markus Schaber
  • Re: simple join uses indexes, very slow Dave Dutcher
  • Re: Massive Inserts Strategies ashah
  • Re: simple join uses indexes, very slow Markus Schaber
  • Re: simple join uses indexes, very slow george young
  • Re: Slow performance on Windows .NET and OleDb Merlin Moncure
  • Slow performance on Windows .NET and OleDb Greg Quinn
  • Re: count(*) performance Markus Schaber
  • Re: simple join uses indexes, very slow Simon Riggs
• 27 March 2006
  • Re: count(*) performance Mikael Carneholm
  • Re: count(*) performance Tom Lane
  • Re: count(*) performance Matthew T. O'Connor
  • Re: count(*) performance Mikael Carneholm
  • Large Binary Objects Middleware Rodrigo Madera
  • Re: count(*) performance Guido Neitzer
  • Re: count(*) performance Alvaro Herrera
  • Re: count(*) performance Matthew T. O'Connor
  • Re: count(*) performance Brendan Duddridge
  • simple join uses indexes, very slow george young
  • Re: count(*) performance Gábriel Ákos
  • Re: count(*) performance Luke Lonergan
  • Re: count(*) performance Gábriel Ákos
  • Re: count(*) performance Gábriel Ákos
  • Re: count(*) performance Luke Lonergan
  • Re: Query parallelism Jim C. Nasby
  • Query parallelism luchot
  • Re: count(*) performance Jim C. Nasby
  • count(*) performance Gábriel Ákos
  • Re: [GENERAL] experiences needed - how does Itanium2/1.5GHz(4MB) compare to AMD and Intel CPUs as far as Postgresql is concerned Jim C. Nasby
  • Re: Array performance Ruben Rubio Rey
• 25 March 2006
  • Re: Query plan from hell Guido Neitzer
  • Re: limitation using LIKE on ANY(array) K C Lau
• 24 March 2006
  • Query plan from hell PFC
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Chris Browne
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Jim C. Nasby
  • Re: Performance problems with multiple layers of functions Tom Lane
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Michael Stone
  • Re: Performance problems with multiple layers of functions Svenne Krap
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Chris Browne
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Chris Browne
  • Re: WAL logging of SELECT ... INTO command Kris Jurka
  • Re: Postmaster using only 4-5% CPU Scott Marlowe
  • Re: limitation using LIKE on ANY(array) Tom Lane
  • Re: Performance problems with multiple layers of functions Tom Lane
  • Re: Array performance Tom Lane
  • limitation using LIKE on ANY(array) K C Lau
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Luke Lonergan
  • Re: Problem with query, server totally unresponsive Jim C. Nasby
  • Re: Problem with query, server totally unresponsive Dave Dutcher
  • Re: WAL logging of SELECT ... INTO command Jim C. Nasby
  • Re: WAL logging of SELECT ... INTO command Alvaro Herrera
  • Re: Array performance Michael Fuhr
  • Re: Array performance Jim C. Nasby
  • Re: Array performance Ruben Rubio Rey
  • Re: WAL logging of SELECT ... INTO command Jim C. Nasby
  • Re: Performance problems with multiple layers of functions Jim C. Nasby
  • Re: Array performance Jim C. Nasby
  • Performance problems with multiple layers of functions Svenne Krap
  • Array performance Ruben Rubio Rey
  • Re: WAL logging of SELECT ... INTO command Alvaro Herrera
  • Re: Problem with query, server totally unresponsive Jim C. Nasby
  • Re: Indexes with descending date columns Jim C. Nasby
  • Re: Postmaster using only 4-5% CPU Jim C. Nasby
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Jim C. Nasby
  • Re: WAL logging of SELECT ... INTO command Jim C. Nasby
  • Re: WAL logging of SELECT ... INTO command Jim C. Nasby
  • Re: Indexes with descending date columns Tom Lane
  • Re: Indexes with descending date columns Theo Kramer
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Christopher Browne
• 23 March 2006
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Scott Marlowe
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Joshua D. Drake
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Scott Marlowe
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Frank Wiles
  • Problem with query, forget previous message Bendik Rognlien Johansen
  • Re: Scaling up PostgreSQL in Multiple CPU / Dual Core Powered Servers Christopher Browne

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