• 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 2007-01 Chronological Index (1/3)

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

• 01 February 2007
  • Re: Slow update Tomas Vondra
  • Re: Very slow queries Chad Wagner
  • Slow update Abu Mushayeed
• 31 January 2007
  • Re: Very slow queries Sidar López Cruz
  • Re: Querying distinct values from a large table Tom Lane
  • Re: Very slow queries Sidar López Cruz
  • Re: Querying distinct values from a large table Ron
  • Re: Very slow queries Ted Allen
  • Re: Very slow queries Sidar López Cruz
  • Re: Querying distinct values from a large table Gregory Stark
  • Re: Querying distinct values from a large table Luke Lonergan
  • Re: Querying distinct values from a large table Tom Lane
• 30 January 2007
  • Re: Querying distinct values from a large table Luke Lonergan
  • Re: Querying distinct values from a large table Alvaro Herrera
  • Re: Querying distinct values from a large table Josh Berkus
  • Re: Very slow queries Chad Wagner
  • Re: Very slow queries Ted Allen
  • Re: Very slow queries Sidar López Cruz
  • Very slow queries Sidar López Cruz
  • Re: Querying distinct values from a large table Steinar H. Gunderson
  • Re: Querying distinct values from a large table Luke Lonergan
  • Re: Querying distinct values from a large table Alvaro Herrera
  • Re: Querying distinct values from a large table Bruno Wolff III
  • Re: Querying distinct values from a large table Gregory Stark
  • Re: Querying distinct values from a large table Luke Lonergan
  • Re: Querying distinct values from a large table Chad Wagner
  • Re: Querying distinct values from a large table Luke Lonergan
  • Re: Bad Row Count Estimate on View with 8.2 Dave Dutcher
  • Re: Querying distinct values from a large table Brian Herlihy
  • Re: Querying distinct values from a large table Chad Wagner
  • Re: Querying distinct values from a large table Richard Huxton
  • Re: Querying distinct values from a large table Simon Riggs
  • Re: Querying distinct values from a large table imad
  • Re: int4 vs varchar to store ip addr Pomarede Nicolas
  • Re: Partitioning Rigmor Ukuhe
  • Re: Tuning John Parnefjord
  • Re: Querying distinct values from a large table Richard Huxton
  • Re: Querying distinct values from a large table Igor Lobanov
  • Re: Querying distinct values from a large table Igor Lobanov
  • Re: Querying distinct values from a large table Richard Huxton
  • Querying distinct values from a large table Igor Lobanov
  • Re: Partitioning Tomas Vondra
  • Partitioning Abu Mushayeed
• 29 January 2007
  • Thanks All! Saranya Sivakumar
  • Re: [OT] Very strange postgresql behaviour Carlos Moreno
  • Re: int4 vs varchar to store ip addr Cosimo Streppone
  • Re: int4 vs varchar to store ip addr Florian Weimer
  • int4 vs varchar to store ip addr Pomarede Nicolas
  • Re: Tuning Ron
  • Re: [OT] Very strange postgresql behaviour Arnau
  • Re: work-mem how do I identify the proper size Bill Moran
  • Re: [OT] Very strange postgresql behaviour Heikki Linnakangas
  • Re: [OT] Very strange postgresql behaviour Bill Moran
  • [OT] Very strange postgresql behaviour Arnau
  • work-mem how do I identify the proper size Campbell, Lance
• 28 January 2007
  • Re: Tuning Tom Lane
  • Re: Tuning Josh Berkus
  • Re: work_mem Bill Moran
  • Re: work-mem imad
  • work-mem Campbell, Lance
  • Re: Bad Row Count Estimate on View with 8.2 Tom Lane
  • Re: Bad Row Count Estimate on View with 8.2 Dave Dutcher
  • Re: IN operator causes sequential scan (vs. multiple OR expressions) Ryan Holmes
  • Re: IN operator causes sequential scan (vs. multiple OR expressions) Tom Lane
  • Re: IN operator causes sequential scan (vs. multiple OR expressions) Ryan Holmes
• 27 January 2007
  • Re: IN operator causes sequential scan (vs. multiple OR expressions) Tom Lane
  • IN operator causes sequential scan (vs. multiple OR expressions) Ryan Holmes
  • Re: Seqscan/Indexscan still a known issue? Carlos Moreno
  • Re: Seqscan/Indexscan still a known issue? Tom Lane
  • Re: Seqscan/Indexscan still a known issue? Carlos Moreno
  • Re: Seqscan/Indexscan still a known issue? Scott Marlowe
  • Re: Seqscan/Indexscan still a known issue? Russell Smith
  • Re: Seqscan/Indexscan still a known issue? Tomas Vondra
  • Re: Seqscan/Indexscan still a known issue? Guido Neitzer
  • Re: Seqscan/Indexscan still a known issue? Russell Smith
  • Re: Seqscan/Indexscan still a known issue? Dennis Bjorklund
  • Seqscan/Indexscan still a known issue? Carlos Moreno
• 26 January 2007
  • Re: [HACKERS] how to plan for vacuum? Jim Nasby
  • Re: Tuning Anton Rommerskirchen
  • Re: Tuning Dave Cramer
  • Tuning John Parnefjord
• 25 January 2007
  • Re: [HACKERS] how to plan for vacuum? Ray Stell
  • Re: [HACKERS] how to plan for vacuum? Joshua D. Drake
  • Re: how to plan for vacuum? Jim C. Nasby
  • Re: how to plan for vacuum? Ray Stell
  • Re: how to plan for vacuum? Galy Lee
  • Re: [HACKERS] how to plan for vacuum? Jim C. Nasby
  • Re: how to plan for vacuum? Alvaro Herrera
  • Re: how to plan for vacuum? Jim C. Nasby
• 24 January 2007
  • Re: slow result Shoaib Mir
  • Re: Auto Vacuum Problem Heiko W.Rupp
  • Re: Auto Vacuum Problem Richard Huxton
  • Re: Postgres processes have a burst of CPU usage Richard Huxton
  • Auto Vacuum Problem Gauri Kanekar
  • Re: how to plan for vacuum? Galy Lee
  • Re: Bad Row Count Estimate on View with 8.2 Tom Lane
  • how to plan for vacuum? Galy Lee
  • Re: extract(field from timestamp) vs date dimension Mark Kirkwood
  • Re: slow result Mark Kirkwood
• 23 January 2007
  • Bad Row Count Estimate on View with 8.2 Dave Dutcher
  • Re: slow result Bruno Wolff III
  • Re: extract(field from timestamp) vs date dimension Merlin Moncure
  • Postgres processes have a burst of CPU usage Subramaniam Aiylam
  • Re: slow result Ron
  • Re: slow result Bill Moran
  • Re: extract(field from timestamp) vs date dimension Tobias Brox
  • Re: extract(field from timestamp) vs date dimension Chad Wagner
  • extract(field from timestamp) vs date dimension Tobias Brox
  • Re: slow result A. Kretschmer
  • slow result Laurent Manchon
  • Re: slow result Steinar H. Gunderson
  • Re: slow result Steinar H. Gunderson
  • Re: slow result A. Kretschmer
  • Re: slow result Heiko W.Rupp
  • slow result Laurent Manchon
• 22 January 2007
  • Re: Table Inheritence and Partioning Simon Riggs
• 20 January 2007
  • Re: [pgsql-advocacy] Postgres and really huge tables Josh Berkus
• 19 January 2007
  • Re: DB benchmark and pg config file help Kevin Hunter
  • Re: Configuration Advice Merlin Moncure
  • Re: DB benchmark and pg config file help Bruno Wolff III
  • Re: Postgres and really huge tables Merlin Moncure
  • Re: DB benchmark and pg config file help Kevin Hunter
  • Re: DB benchmark and pg config file help Merlin Moncure
  • Re: [pgsql-advocacy] Postgres and really huge tables Oleg Bartunov
  • Re: Configuration Advice Arjen van der Meijden
• 18 January 2007
  • Re: Postgres and really huge tables Gavin Sherry
  • Re: [pgsql-advocacy] Postgres and really huge tables Luke Lonergan
  • Re: Configuration Advice Tom Lane
  • Re: Autoanalyze settings with zero scale factor Jeremy Haile
  • Re: Postgres and really huge tables Tom Lane
  • Re: [pgsql-advocacy] Postgres and really huge tables Chris Mair
  • Re: Autoanalyze settings with zero scale factor Tom Lane
  • Re: Configuration Advice Arjen van der Meijden
  • Re: Postgres and really huge tables Scott Marlowe
  • Re: Autoanalyze settings with zero scale factor Matthew T. O'Connor
  • Re: [pgsql-advocacy] Postgres and really huge tables Joshua D. Drake
  • Postgres and really huge tables Brian Hurt
  • Re: Autoanalyze settings with zero scale factor Jeremy Haile
  • Re: Autoanalyze settings with zero scale factor Matthew T. O'Connor
  • Autoanalyze settings with zero scale factor Jeremy Haile
  • Re: Configuration Advice Jeremy Haile
  • Re: Configuration Advice Arjen van der Meijden
  • Re: Configuration Advice Scott Marlowe
  • Re: Configuration Advice Scott Marlowe
  • Re: Vacuum v/s Autovacuum Shoaib Mir
  • Re: Vacuum v/s Autovacuum Bill Moran
  • Re: Vacuum v/s Autovacuum Gauri Kanekar
  • Re: Vacuum v/s Autovacuum Michael Glaesemann
  • Vacuum v/s Autovacuum Gauri Kanekar
  • Re: Configuration Advice Arjen van der Meijden
  • Re: Monitoring Transaction Log size Shoaib Mir
  • Re: Monitoring Transaction Log size Simon Riggs
  • Re: Version Change Michael Glaesemann
  • Re: Version Change Michael Glaesemann
  • Re: Version Change Michael Glaesemann
  • Version Change Gauri Kanekar
  • Re: Configuration Advice Steve
  • Re: Configuration Advice Steve
  • Re: Configuration Advice Steve
  • Re: Configuration Advice Chris Browne
  • Re: Configuration Advice Chad Wagner
• 17 January 2007
  • Re: Configuration Advice Steve
  • Re: Configuration Advice Steve
  • Re: Configuration Advice Dave Cramer
  • Re: Configuration Advice Adam Rich
  • Re: Configuration Advice Steve
  • Re: Configuration Advice Scott Marlowe
  • Re: Monitoring Transaction Log size Tom Lane
  • DB benchmark and pg config file help Kevin Hunter
  • Re: Configuration Advice Bruno Wolff III
  • Re: Configuration Advice Joshua D. Drake
  • Re: Configuration Advice Benjamin Minshall
  • Re: Configuration Advice Steve
  • Re: Configuration Advice Steve
  • Re: Configuration Advice Heikki Linnakangas
  • Re: Configuration Advice Chad Wagner
  • Re: Configuration Advice Tomas Vondra
  • Re: Configuration Advice Bricklen Anderson
  • Re: Configuration Advice Adam Rich
  • Configuration Advice Steve

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