pgsql-performance 2007-01 Thread Index (1/3)

Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Text Size: Normal / Large
Donate
Contact

Header And Logo

PostgreSQL

|

The world's most advanced open source database.

Site Navigation

pgsql-performance 2007-01 Thread Index (1/3)

Last updated: Wed Jan 18 04:17:47 2012
453 messages

Main Index
[Prev Page]
[Next Page]

Slow update Abu Mushayeed (Thu 01 00:57)

Re: Slow update Tomas Vondra (Thu 01 01:32)

Very slow queries Sidar López Cruz (Tue 30 21:09)

Re: Very slow queries Ted Allen (Tue 30 21:46)

Re: Very slow queries Sidar López Cruz (Tue 30 21:19)

Re: Very slow queries Chad Wagner (Tue 30 22:37)

Re: Very slow queries Sidar López Cruz (Wed 31 14:19)

Re: Very slow queries Ted Allen (Wed 31 14:32)

Re: Very slow queries Sidar López Cruz (Wed 31 14:58)
Re: Very slow queries Sidar López Cruz (Wed 31 15:28)

Re: Very slow queries Chad Wagner (Thu 01 01:30)

Querying distinct values from a large table Igor Lobanov (Tue 30 08:59)

Re: Querying distinct values from a large table Richard Huxton (Tue 30 09:13)

Re: Querying distinct values from a large table Igor Lobanov (Tue 30 09:33)

Re: Querying distinct values from a large table Richard Huxton (Tue 30 10:02)

Re: Querying distinct values from a large table imad (Tue 30 11:39)

Re: Querying distinct values from a large table Simon Riggs (Tue 30 14:06)

Re: Querying distinct values from a large table Richard Huxton (Tue 30 14:12)
Re: Querying distinct values from a large table Chad Wagner (Tue 30 14:13)

Re: Querying distinct values from a large table Luke Lonergan (Tue 30 14:57)
Re: Querying distinct values from a large table Chad Wagner (Tue 30 15:03)
Re: Querying distinct values from a large table Luke Lonergan (Tue 30 16:34)
Re: Querying distinct values from a large table Gregory Stark (Tue 30 16:39)
Re: Querying distinct values from a large table Alvaro Herrera (Tue 30 18:07)
Re: Querying distinct values from a large table Luke Lonergan (Tue 30 20:56)
Re: Querying distinct values from a large table Steinar H. Gunderson (Tue 30 21:00)
Re: Querying distinct values from a large table Josh Berkus (Tue 30 22:57)
Re: Querying distinct values from a large table Luke Lonergan (Tue 30 23:18)
Re: Querying distinct values from a large table Alvaro Herrera (Tue 30 23:07)
Re: Querying distinct values from a large table Tom Lane (Wed 31 05:55)
Re: Querying distinct values from a large table Luke Lonergan (Wed 31 06:59)
Re: Querying distinct values from a large table Gregory Stark (Wed 31 13:25)
Re: Querying distinct values from a large table Ron (Wed 31 14:46)
Re: Querying distinct values from a large table Tom Lane (Wed 31 15:16)

Re: Querying distinct values from a large table Igor Lobanov (Tue 30 09:36)

Re: Querying distinct values from a large table Bruno Wolff III (Tue 30 17:00)
<Possible follow-ups>
Re: Querying distinct values from a large table Brian Herlihy (Tue 30 14:38)

Thanks All! Saranya Sivakumar (Mon 29 20:51)
int4 vs varchar to store ip addr Pomarede Nicolas (Mon 29 16:22)

Re: int4 vs varchar to store ip addr Florian Weimer (Mon 29 16:26)

Re: int4 vs varchar to store ip addr Pomarede Nicolas (Tue 30 10:54)

Re: int4 vs varchar to store ip addr Cosimo Streppone (Mon 29 17:21)

[OT] Very strange postgresql behaviour Arnau (Mon 29 12:22)

Re: [OT] Very strange postgresql behaviour Bill Moran (Mon 29 13:27)

Re: [OT] Very strange postgresql behaviour Arnau (Mon 29 15:41)

Re: [OT] Very strange postgresql behaviour Carlos Moreno (Mon 29 19:43)

Re: [OT] Very strange postgresql behaviour Heikki Linnakangas (Mon 29 13:36)

work-mem how do I identify the proper size Campbell, Lance (Mon 29 03:07)

Re: work-mem how do I identify the proper size Bill Moran (Mon 29 14:54)

work-mem Campbell, Lance (Sun 28 20:18)

Re: work-mem imad (Sun 28 20:26)
Re: work_mem Bill Moran (Sun 28 22:11)

IN operator causes sequential scan (vs. multiple OR expressions) Ryan Holmes (Sat 27 23:35)

Re: IN operator causes sequential scan (vs. multiple OR expressions) Tom Lane (Sat 27 23:53)

Re: IN operator causes sequential scan (vs. multiple OR expressions) Ryan Holmes (Sun 28 01:34)

Re: IN operator causes sequential scan (vs. multiple OR expressions) Tom Lane (Sun 28 01:56)

Re: IN operator causes sequential scan (vs. multiple OR expressions) Ryan Holmes (Sun 28 02:32)

Seqscan/Indexscan still a known issue? Carlos Moreno (Sat 27 03:14)

Re: Seqscan/Indexscan still a known issue? Dennis Bjorklund (Sat 27 07:26)
Re: Seqscan/Indexscan still a known issue? Russell Smith (Sat 27 07:35)

Re: Seqscan/Indexscan still a known issue? Guido Neitzer (Sat 27 08:38)

Re: Seqscan/Indexscan still a known issue? Russell Smith (Sat 27 10:44)

Re: Seqscan/Indexscan still a known issue? Scott Marlowe (Sat 27 11:34)

Re: Seqscan/Indexscan still a known issue? Tomas Vondra (Sat 27 09:54)

Re: Seqscan/Indexscan still a known issue? Carlos Moreno (Sat 27 17:11)

Re: Seqscan/Indexscan still a known issue? Tom Lane (Sat 27 17:28)

Re: Seqscan/Indexscan still a known issue? Carlos Moreno (Sat 27 21:10)

Tuning John Parnefjord (Fri 26 11:28)

Re: Tuning Dave Cramer (Fri 26 14:07)
Re: Tuning Anton Rommerskirchen (Fri 26 16:22)
Re: Tuning Josh Berkus (Sun 28 23:23)

Re: Tuning Tom Lane (Sun 28 23:38)
Re: Tuning Ron (Mon 29 16:15)

Re: Tuning John Parnefjord (Tue 30 10:05)

Auto Vacuum Problem Gauri Kanekar (Wed 24 08:49)

Re: Auto Vacuum Problem Richard Huxton (Wed 24 08:54)
Re: Auto Vacuum Problem Heiko W.Rupp (Wed 24 09:14)

how to plan for vacuum? Galy Lee (Wed 24 05:38)

Re: how to plan for vacuum? Galy Lee (Wed 24 07:45)
Re: how to plan for vacuum? Jim C. Nasby (Thu 25 03:39)

Re: how to plan for vacuum? Alvaro Herrera (Thu 25 03:52)

Re: [HACKERS] how to plan for vacuum? Jim C. Nasby (Thu 25 03:57)
Re: [HACKERS] how to plan for vacuum? Joshua D. Drake (Thu 25 16:02)

Re: [HACKERS] how to plan for vacuum? Ray Stell (Thu 25 16:33)

Re: [HACKERS] how to plan for vacuum? Jim Nasby (Fri 26 21:08)

Re: how to plan for vacuum? Galy Lee (Thu 25 10:29)

Re: how to plan for vacuum? Ray Stell (Thu 25 13:47)

Message not available
- Re: how to plan for vacuum? Jim C. Nasby (Thu 25 15:54)

Bad Row Count Estimate on View with 8.2 Dave Dutcher (Tue 23 22:08)

Re: Bad Row Count Estimate on View with 8.2 Tom Lane (Wed 24 07:44)

Re: Bad Row Count Estimate on View with 8.2 Dave Dutcher (Sun 28 17:09)

Re: Bad Row Count Estimate on View with 8.2 Tom Lane (Sun 28 18:48)

Re: Bad Row Count Estimate on View with 8.2 Dave Dutcher (Tue 30 14:54)

Postgres processes have a burst of CPU usage Subramaniam Aiylam (Tue 23 16:11)

Re: Postgres processes have a burst of CPU usage Richard Huxton (Wed 24 08:49)

extract(field from timestamp) vs date dimension Tobias Brox (Tue 23 12:49)

Re: extract(field from timestamp) vs date dimension Chad Wagner (Tue 23 13:24)

Re: extract(field from timestamp) vs date dimension Tobias Brox (Tue 23 13:35)

Re: extract(field from timestamp) vs date dimension Mark Kirkwood (Wed 24 03:21)

Re: extract(field from timestamp) vs date dimension Merlin Moncure (Tue 23 16:23)

slow result Laurent Manchon (Tue 23 10:35)

Re: slow result Heiko W.Rupp (Tue 23 10:44)
Re: slow result A. Kretschmer (Tue 23 10:53)
Re: slow result Steinar H. Gunderson (Tue 23 10:55)

Re: slow result Steinar H. Gunderson (Tue 23 10:58)

Re: slow result Bill Moran (Tue 23 13:53)
Re: slow result Bruno Wolff III (Tue 23 17:59)

Re: slow result Shoaib Mir (Wed 24 10:19)

<Possible follow-ups>
slow result Laurent Manchon (Tue 23 12:34)

Re: slow result A. Kretschmer (Tue 23 12:43)
Re: slow result Ron (Tue 23 14:43)
Re: slow result Mark Kirkwood (Wed 24 00:52)

Postgres and really huge tables Brian Hurt (Thu 18 20:31)

Re: [pgsql-advocacy] Postgres and really huge tables Joshua D. Drake (Thu 18 20:36)
Re: Postgres and really huge tables Scott Marlowe (Thu 18 21:04)
Re: [pgsql-advocacy] Postgres and really huge tables Chris Mair (Thu 18 21:43)

Re: [pgsql-advocacy] Postgres and really huge tables Luke Lonergan (Thu 18 22:42)
Re: [pgsql-advocacy] Postgres and really huge tables Josh Berkus (Sat 20 00:01)

Re: Postgres and really huge tables Tom Lane (Thu 18 21:53)

Re: [pgsql-advocacy] Postgres and really huge tables Oleg Bartunov (Fri 19 10:03)

Re: Postgres and really huge tables Gavin Sherry (Thu 18 23:10)
Re: Postgres and really huge tables Merlin Moncure (Fri 19 14:11)

Autoanalyze settings with zero scale factor Jeremy Haile (Thu 18 18:37)

Re: Autoanalyze settings with zero scale factor Matthew T. O'Connor (Thu 18 19:20)

Re: Autoanalyze settings with zero scale factor Jeremy Haile (Thu 18 20:21)

Re: Autoanalyze settings with zero scale factor Matthew T. O'Connor (Thu 18 20:40)
Re: Autoanalyze settings with zero scale factor Tom Lane (Thu 18 21:30)

Re: Autoanalyze settings with zero scale factor Jeremy Haile (Thu 18 21:53)

Vacuum v/s Autovacuum Gauri Kanekar (Thu 18 13:24)

Re: Vacuum v/s Autovacuum Michael Glaesemann (Thu 18 13:31)

Re: Vacuum v/s Autovacuum Gauri Kanekar (Thu 18 13:46)

Re: Vacuum v/s Autovacuum Bill Moran (Thu 18 14:05)

Re: Vacuum v/s Autovacuum Shoaib Mir (Thu 18 14:14)

Version Change Gauri Kanekar (Thu 18 04:43)

Re: Version Change Michael Glaesemann (Thu 18 04:57)

Re: Version Change Michael Glaesemann (Thu 18 05:00)

Message not available
- Re: Version Change Michael Glaesemann (Thu 18 05:35)

DB benchmark and pg config file help Kevin Hunter (Wed 17 22:16)

Re: DB benchmark and pg config file help Merlin Moncure (Fri 19 13:46)

Re: DB benchmark and pg config file help Kevin Hunter (Fri 19 14:06)

Re: DB benchmark and pg config file help Bruno Wolff III (Fri 19 16:52)

Re: DB benchmark and pg config file help Kevin Hunter (Fri 19 21:41)

Re: Configuration Advice Adam Rich (Wed 17 21:24)

Re: Configuration Advice Bricklen Anderson (Wed 17 21:29)

Re: Configuration Advice Joshua D. Drake (Wed 17 22:12)
Re: Configuration Advice Adam Rich (Wed 17 23:37)

Re: Configuration Advice Steve (Thu 18 00:30)
Re: Configuration Advice Arjen van der Meijden (Thu 18 10:52)

Re: Configuration Advice Scott Marlowe (Thu 18 16:21)

Re: Configuration Advice Arjen van der Meijden (Thu 18 16:42)

Re: Configuration Advice Jeremy Haile (Thu 18 17:28)

Re: Configuration Advice Arjen van der Meijden (Thu 18 21:10)
Re: Configuration Advice Tom Lane (Thu 18 22:11)
Re: Configuration Advice Arjen van der Meijden (Fri 19 06:15)

Re: Configuration Advice Bruno Wolff III (Wed 17 22:12)

Re: Configuration Advice Steve (Wed 17 23:57)

Monitoring Transaction Log size Ziegelwanger, Silvio (Wed 17 17:29)

Re: Monitoring Transaction Log size Joshua D. Drake (Wed 17 17:54)

Re: Monitoring Transaction Log size Shoaib Mir (Wed 17 18:04)

Re: Monitoring Transaction Log size Simon Riggs (Thu 18 09:57)

Re: Monitoring Transaction Log size Shoaib Mir (Thu 18 10:19)

Re: Monitoring Transaction Log size Stefan Kaltenbrunner (Wed 17 18:30)
Re: Monitoring Transaction Log size Tom Lane (Wed 17 22:39)

Raid 10 or Raid 5 on Dell PowerEdge Dave Dutcher (Wed 17 15:57)
Table Inheritence and Partioning ramachandra.bhaskaram (Wed 17 10:43)

Re: Table Inheritence and Partioning Albert Cervera Areny (Wed 17 11:04)
Re: Table Inheritence and Partioning Simon Riggs (Mon 22 09:42)

PG8.2.1 choosing slow seqscan over idx scan Jeremy Haile (Tue 16 21:23)

Re: PG8.2.1 choosing slow seqscan over idx scan Tom Lane (Tue 16 21:39)

Re: PG8.2.1 choosing slow seqscan over idx scan Jeremy Haile (Tue 16 22:21)

Re: PG8.2.1 choosing slow seqscan over idx scan Chad Wagner (Tue 16 22:45)

Re: PG8.2.1 choosing slow seqscan over idx scan Jeremy Haile (Wed 17 03:01)

Re: PG8.2.1 choosing slow seqscan over idx scan Chad Wagner (Wed 17 04:53)
Re: PG8.2.1 choosing slow seqscan over idx scan Jeremy Haile (Wed 17 15:12)
Re: PG8.2.1 choosing slow seqscan over idx scan Chad Wagner (Wed 17 17:27)
Re: PG8.2.1 choosing slow seqscan over idx scan Jeremy Haile (Wed 17 18:47)
Re: PG8.2.1 choosing slow seqscan over idx scan Scott Marlowe (Wed 17 05:47)
Re: PG8.2.1 choosing slow seqscan over idx scan Jeremy Haile (Wed 17 14:38)
Re: PG8.2.1 choosing slow seqscan over idx scan Shoaib Mir (Wed 17 14:53)
Re: PG8.2.1 choosing slow seqscan over idx scan Dave Cramer (Wed 17 15:14)

Main Index
[Prev Page]
[Next Page]

Mail converted by MHonArc

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group