Архив рассылок [pgsql-performance]
Re: Huge Data sets, simple queries Jeffrey W. Baker
Re: Sequential scan being used despite indexes James Russell
Re: Sequential scan being used despite indexes Christopher Kings-Lynne
Re: Sequential scan being used despite indexes Michael Fuhr
Re: Huge Data sets, simple queries Luke Lonergan
Re: Huge Data sets, simple queries Jeffrey W. Baker
Re: partitioning and locking problems Richard Huxton
execution plan : Oracle vs PostgreSQL FERREIRA, William (VALTECH)
Re: Huge Data sets, simple queries Michael Stone
Re: partitioning and locking problems Marc Morin
Re: execution plan : Oracle vs PostgreSQL FERREIRA, William (VALTECH)
Re: Huge Data sets, simple queries Luke Lonergan
Re: Huge Data sets, simple queries Steinar H. Gunderson
Re: Huge Data sets, simple queries Mike Rylander
Planner reluctant to start from subquery Kevin Grittner
Re: Planner reluctant to start from subquery Kevin Grittner
Index Usage using IN Ralph Mason
Re: Index Usage using IN Jeffrey W. Baker
Re: Planner reluctant to start from subquery Kevin Grittner
Re: Index Usage using IN Jeffrey W. Baker
Re: Index Usage using IN Tom Lane
Re: Planner reluctant to start from subquery Kevin Grittner
Re: Planner reluctant to start from subquery Kevin Grittner
Re: Index Usage using IN Bruno Wolff III
Default autovacuum settings too conservative Jim C. Nasby
Re: Default autovacuum settings too conservative Matthew T. O'Connor
Re: Index Usage using IN Hari Warrier
Re: Huge Data sets, simple queries Luke Lonergan
pgbench output Pradeep Parmar
Re: Where is my bottleneck? Markus Schaber
Re: partitioning and locking problems Markus Schaber
Re: partitioning and locking problems Marc Morin
Re: Huge Data sets, simple queries Alan Stange
Re: Storing Digital Video Albert Cervera Areny
Re: Default autovacuum settings too conservative Vivek Khera
Re: execution plan : Oracle vs PostgreSQL Andrew Lazarus
Re: Default autovacuum settings too conservative Chris Browne
Re: partitioning and locking problems Jim C. Nasby
Re: Default autovacuum settings too conservative Jim C. Nasby
Re: pgbench output Jim C. Nasby
Re: Default autovacuum settings too conservative Christopher Browne
Re: Default autovacuum settings too conservative Jim C. Nasby
Re: Default autovacuum settings too conservative Markus Schaber
Re: Default autovacuum settings too conservative Michael Stone
Re: partitioning and locking problems Simon Riggs
Re: partitioning and locking problems Marc Morin
Re: partitioning and locking problems Jim C. Nasby
Re: Default autovacuum settings too conservative Jim C. Nasby
Re: Default autovacuum settings too conservative Russell Smith
Re: Default autovacuum settings too conservative Christopher Browne
Re: partitioning and locking problems Simon Riggs
Re: Default autovacuum settings too conservative Markus Schaber
optimizing away join when querying view Jacob Costello
Re: optimizing away join when querying view Stephan Szabo
Re: Size and performance hit from using UTF8 vs. ASCII? Jeffrey W. Baker
Re: Default autovacuum settings too conservative Markus Schaber
Re: Default autovacuum settings too conservative Markus Schaber
Re: Storing Digital Video Nate Byrnes
Help with optimizing a sql statement Rafael Martinez Guerrero
Re: Storing Digital Video Craig A. James
Re: Storing Digital Video Nate Byrnes
Large Database Design Help Orion Henry
Re: Storing Digital Video Jim C. Nasby
Re: Help with optimizing a sql statement Jim C. Nasby
Re: Help with optimizing a sql statement Dave Dutcher
Re: Large Database Design Help Jim C. Nasby
Re: Large Database Design Help Greg Stark
Re: Help with optimizing a sql statement Jim C. Nasby
Re: Large Database Design Help Matthew Nuzum
Re: Help with optimizing a sql statement Rafael Martinez
Re: Storing Digital Video Jan Peterson
Re: Help with optimizing a sql statement Rafael Martinez
Re: Help with optimizing a sql statement Vivek Khera
Re: Help with optimizing a sql statement Greg Stark
10+hrs vs 15min because of just one index Aaron Turner
Basic Database Performance James Dey
Re: 10+hrs vs 15min because of just one index hubert depesz lubaczewski
Re: Basic Database Performance Richard Huxton
Re: Basic Database Performance Richard Huxton
Re: Basic Database Performance James Dey
Re: Large Database Design Help Markus Schaber
Re: Large Database Design Help Markus Schaber
Re: Basic Database Performance Markus Schaber
Re: pgbench output Gourish Singbal
Re: 10+hrs vs 15min because of just one index Aaron Turner
Re: 10+hrs vs 15min because of just one index Matthew T. O'Connor
Re: 10+hrs vs 15min because of just one index Aaron Turner
help required in design of database david drummard
Re: help required in design of database Steinar H. Gunderson
Re: joining two tables slow due to sequential scan Dave Dutcher
Re: joining two tables slow due to sequential scan Scott Marlowe
Re: joining two tables slow due to sequential scan Scott Marlowe
Re: joining two tables slow due to sequential scan Scott Marlowe
Re: Large Database Design Help Scott Marlowe
Re: joining two tables slow due to sequential scan Scott Marlowe
Re: joining two tables slow due to sequential scan Dave Dutcher
postgresql geqo optimization uwcssa
Re: postgresql geqo optimization Steinar H. Gunderson
Re: 10+hrs vs 15min because of just one index Aaron Turner
Re: 10+hrs vs 15min because of just one index Aaron Turner
Re: 10+hrs vs 15min because of just one index Aaron Turner
SQL Function Performance Adnan DURSUN
Re: SQL Function Performance andrew@pillette.com
Re: 10+hrs vs 15min because of just one index Markus Schaber
Re: SQL Function Performance Michael Fuhr
Re: help required in design of database Markus Schaber
Re: SQL Function Performance Adnan DURSUN
Re: SQL Function Performance Adnan DURSUN
Re: SQL Function Performance Adnan DURSUN
Re: SQL Function Performance Adnan DURSUN
Re: SQL Function Performance Tom Lane
Re: SQL Function Performance Michael Fuhr
Re: SQL Function Performance Adnan DURSUN
copy and postgresql.conf FERREIRA, William (VALTECH)
Re: copy and postgresql.conf Albert Cervera Areny
Re: copy and postgresql.conf FERREIRA, William (VALTECH)
out of memory martial.bizel@free.fr
Re: out of memory Tom Lane
Postgres slower than MS ACCESS Jay Greenfield
Re: out of memory martial.bizel@free.fr
Re: Postgres slower than MS ACCESS Scott Marlowe
Re: out of memory Scott Marlowe
Re: copy and postgresql.conf Albert Cervera Areny
Re: out of memory martial.bizel@free.fr
Re: Postgres slower than MS ACCESS Jay Greenfield
Re: out of memory Scott Marlowe
Re: Postgres slower than MS ACCESS Scott Marlowe
Re: out of memory martial.bizel@free.fr
0ut of Memory Error during Vacuum Analyze Tomeh, Husam
Re: out of memory Scott Marlowe
Re: copy and postgresql.conf FERREIRA, William (VALTECH)
Re: Postgres slower than MS ACCESS Stephen Frost
Re: out of memory Tom Lane
Re: out of memory Scott Marlowe
Re: Postgres slower than MS ACCESS Tom Lane
Re: Postgres slower than MS ACCESS Stephen Frost
Re: Postgres slower than MS ACCESS Jay Greenfield
Re: Postgres slower than MS ACCESS Tom Lane
Re: SQL Function Performance Michael Fuhr
Re: Postgres slower than MS ACCESS Jay Greenfield
8.2.1 on FreeBSD 5.4-RELEASE Paul Khavkine
Re: copy and postgresql.conf Jignesh K. Shah
Re: 0ut of Memory Error during Vacuum Analyze and Tomeh, Husam
Re: SQL Function Performance Adnan DURSUN
Re: 10+hrs vs 15min because of just one index Aaron Turner
Re: 0ut of Memory Error during Vacuum Analyze and Tomeh, Husam
could not send data to client: Broken pipe Pradeep Parmar
Re: could not send data to client: Broken pipe Richard Huxton
Re: copy and postgresql.conf FERREIRA, William (VALTECH)
Re: copy and postgresql.conf Markus Schaber
Re: copy and postgresql.conf FERREIRA, William (VALTECH)
Re: copy and postgresql.conf Jignesh K. Shah
Re: Postgres slower than MS ACCESS Jeff Trout
Re: copy and postgresql.conf FERREIRA, William (VALTECH)
Re: copy and postgresql.conf Jignesh K. Shah
Re: copy and postgresql.conf Tom Lane
Stored proc and optimizer question Antal Attila
out of memory martial.bizel@free.fr
Re: explain hashAggregate martial.bizel@free.fr
Reliability recommendations Jeremy Haile
Re: out of memory martial.bizel@free.fr
Re: out of memory Scott Marlowe
Re: out of memory martial.bizel@free.fr
Re: Reliability recommendations Craig A. James
Re: Reliability recommendations Mark Lewis
Re: out of memory Scott Marlowe
Re: Reliability recommendations Joshua D. Drake
Re: Reliability recommendations Greg Stark
Re: Reliability recommendations Christopher Browne
Re: Reliability recommendations Scott Marlowe
Strange Create Index behaviour Gary Doades
Re: Strange Create Index behaviour Tom Lane
Re: Reliability recommendations Jeremy Haile
Re: Strange Create Index behaviour Gary Doades
Re: Strange Create Index behaviour Gary Doades
Re: Strange Create Index behaviour Simon Riggs
Re: Strange Create Index behaviour Tom Lane
Re: Postgres slower than MS ACCESS Jay Greenfield
Re: Strange Create Index behaviour Gary Doades
Re: Postgres slower than MS ACCESS Tom Lane
Re: Strange Create Index behaviour Tom Lane
Re: Reliability recommendations Josh Rovero
Re: Strange Create Index behaviour Tom Lane
Re: Strange Create Index behaviour Gary Doades
Re: Strange Create Index behaviour Simon Riggs
Re: qsort again (was Re: Strange Create Index behaviour) Christopher Kings-Lynne
Re: Strange Create Index behaviour Simon Riggs
Re: qsort again (was Re: Strange Create Index Steinar H. Gunderson
Re: [HACKERS] qsort again Florian Weimer
Re: [HACKERS] qsort again Martijn van Oosterhout
Re: [HACKERS] qsort again Sven Geisler
Re: Postgres slower than MS ACCESS Peter Childs
Re: qsort again (was Re: Strange Create Index Markus Schaber
Re: [HACKERS] qsort again (was Re: Strange Create Index Martijn van Oosterhout
Re: qsort again (was Re: Strange Create Index Craig A. James
Re: [HACKERS] qsort again (was Re: Strange Create Martijn van Oosterhout
Why does not perform index combination Adnan DURSUN
Re: qsort again (was Re: Strange Create Index Neil Conway
Re: Why does not perform index combination Adnan DURSUN
Re: [HACKERS] qsort again (was Re: Strange Create Index Markus Schaber
Re: [HACKERS] qsort again (was Re: Strange Create Index Martijn van Oosterhout
Re: [HACKERS] qsort again (was Re: Strange Create Index Markus Schaber
Re: [HACKERS] qsort again (was Re: Strange Create Index Steinar H. Gunderson
split partitioned table across several postgres servers martial.bizel@free.fr
Re: [HACKERS] qsort again (was Re: Strange Create Index Markus Schaber
Re: [HACKERS] qsort again (was Re: Strange Create Markus Schaber
Re: split partitioned table across several postgres servers martial.bizel@free.fr
Re: [HACKERS] qsort again (was Re: Strange Create Martijn van Oosterhout
Re: [HACKERS] qsort again (was Re: Strange Create Index Martijn van Oosterhout
Re: Need pointers to "standard" pg database(s) for Scott Marlowe
Re: SQL Function Performance Mark Liberman
Re: SQL Function Performance Mark Liberman
Re: out of memory martial.bizel@free.fr
Re: [HACKERS] qsort again (was Re: Strange Create Index Jonah H. Harris
Future of Table Partitioning Patrick Carriere
Index Choice Problem Adam Alkins
Measuring Lock Performance Lane Van Ingen
Re: [HACKERS] qsort again (was Re: Strange Create Gregory Maxwell
Stored proc and optimizer question Antal Attila
Re: Index Choice Problem Tom Lane
Re: Index Choice Problem Adam Alkins
Re: Index Choice Problem Adam Alkins
Force another plan. Fredrik Olsson
Re: Force another plan. Tom Lane
Re: Force another plan. Fredrik Olsson
Question about query planner Emil Briggs
Re: Force another plan. Tom Lane
Re: Question about query planner Tom Lane
Re: Need pointers to "standard" pg database(s) for testing Christopher Kings-Lynne
How to optimize a JOIN with BETWEEN? andrew@pillette.com
Re: Need pointers to "standard" pg database(s) for Christopher Kings-Lynne
Re: Avoiding cartesian product Virag Saksena
Re: Force another plan. Fredrik Olsson
Re: Force another plan. Tom Lane
Cost Issue - How do I force a Hash Join Virag Saksena
Re: Cost Issue - How do I force a Hash Join Craig A. James
Re: Cost Issue - How do I force a Hash Join Virag Saksena
LIKE query on indexes Ibrahim Tekin
Re: LIKE query on indexes Scott Marlowe
Re: LIKE query on indexes Alvaro Herrera
Re: LIKE query on indexes Scott Marlowe
Re: LIKE query on indexes mark@mark.mielke.cc
Re: LIKE query on indexes Ibrahim Tekin
Help with nested loop left join performance George Woodring
Re: LIKE query on indexes Ibrahim Tekin
Re: How to optimize a JOIN with BETWEEN? Jim C. Nasby
Re: Help with nested loop left join performance Richard Huxton
Re: Richard Huxton
Re: Gourish Singbal
Re: --pls reply ASAP Richard Huxton
Re: LIKE query on indexes Brendan Duddridge
Re: Vivek Khera
Good News re count(*) in 8.1 Kevin Grittner
Re: Good News re count(*) in 8.1 Luke Lonergan
Re: --pls reply ASAP Theodore LoScalzo
Re: Good News re count(*) in 8.1 Tom Lane
Re: Joins and full index scans...mysql vs postgres? Steinar H. Gunderson
Re: Joins and full index scans...mysql vs postgres? Stephan Szabo
Re: Joins and full index scans...mysql vs postgres? Scott Marlowe
Slow query Jeremy Haile
Re: Joins and full index scans...mysql vs postgres? Christopher Kings-Lynne
Re: Good News re count(*) in 8.1 Greg Stark
Re: Joins and full index scans...mysql vs postgres? Andreas Pflug
Created Index is not used Kjeld Peters
Re: LIKE query on indexes Ibrahim Tekin
Re: Created Index is not used Markus Schaber
Re: Created Index is not used Kjeld Peters
Re: Vivek Khera
how to interpret/improve bad row estimates Robert Treat
Looking for a tool to "*" pg tables as ERDs Ron Peacetree
Re: Looking for a tool to "*" pg tables as ERDs Markus Schaber
Re: Looking for a tool to "*" pg tables as ERDs Vivek Khera
Re: Slow query Tom Lane
Re: Good News re count(*) in 8.1 Kevin Grittner
Re: 0ut of Memory Error during Vacuum Analyze and Tomeh, Husam
Re: Jim C. Nasby
Re: Good News re count(*) in 8.1 Jim C. Nasby
Re: 0ut of Memory Error during Vacuum Analyze and Tomeh, Husam
Really really slow query. What's a better way? Brendan Duddridge
Re: Really really slow query. What's a better way? Christopher Kings-Lynne
Re: Really really slow query. What's a better way? Brendan Duddridge
Re: Reliability recommendations Bruce Momjian
Re: Reliability recommendations Craig A. James
Re: Reliability recommendations Luke Lonergan
Re: Reliability recommendations Luke Lonergan
Re: Reliability recommendations Vivek Khera
Re: Reliability recommendations Scott Marlowe
Re: Reliability recommendations Vivek Khera
Re: Reliability recommendations Scott Marlowe
Re: Reliability recommendations Joshua D. Drake
Re: Reliability recommendations Craig A. James
Re: Reliability recommendations Scott Marlowe
Re: Reliability recommendations Luke Lonergan
Re: Reliability recommendations Philippe Marzin
Re: Reliability recommendations Mark Kirkwood
Re: Reliability recommendations Dan Gorman
Re: Reliability recommendations Mark Kirkwood
Re: Bruce Momjian
Re: Reliability recommendations Luke Lonergan
Re: Reliability recommendations Mark Kirkwood
Re: Reliability recommendations Luke Lonergan
Re: Reliability recommendations Mark Kirkwood
Re: Reliability recommendations Luke Lonergan
fsync and battery-backed caches Javier Somoza
Re: fsync and battery-backed caches Tino Wildenhain
wal sync method Evgeny Gridasov
Re: wal sync method Javier Somoza
Setting the shared buffers Javier Somoza
Re: Setting the shared buffers Claus Guttesen
neverending vacuum Csaba Nagy
Re: neverending vacuum Alvaro Herrera
Re: neverending vacuum Csaba Nagy
The trigger can be specified to fire on time condition? Jamal Ghaffour
Re: The trigger can be specified to fire on time condition? Alvaro Herrera
Re: Large Table With Only a Few Rows Chris Browne
Re: Large Table With Only a Few Rows Peter Childs
Re: fsync and battery-backed caches Jim C. Nasby
Re: fsync and battery-backed caches Bruce Momjian
Re: wal sync method Bruce Momjian
Re: rotate records Bruno Wolff III
Re: fsync and battery-backed caches Javier Somoza
Different disks for xlogs and data Javier Somoza
vacuum, analyze and reindex Javier Somoza
Re: vacuum, analyze and reindex Christopher Browne
temporary indexes Kevin Grittner
Re: [HACKERS] temporary indexes Jim C. Nasby
Re: temporary indexes Tom Lane
Re: [HACKERS] temporary indexes Tom Lane
Re: fsync and battery-backed caches Jim C. Nasby
Re: [HACKERS] temporary indexes Kevin Grittner
Re: fsync and battery-backed caches Javier Somoza
Re: [HACKERS] temporary indexes Kevin Grittner
Re: [HACKERS] temporary indexes Tom Lane
Re: [HACKERS] temporary indexes Steinar H. Gunderson
Re: [HACKERS] temporary indexes Kevin Grittner
Re: [HACKERS] temporary indexes Jim C. Nasby
Re: fsync and battery-backed caches Jim C. Nasby
Re: [HACKERS] temporary indexes Kevin Grittner
Re: wal sync method Tom Lane
Re: triggers, performance Was: Re: [GENERAL] rotate records Jeevanandam, Kathirvel (IE10)