• Text Size: Normal / Large
• Donate
• Contact

Section Navigation

• Community
• Contributors
• Mailing Lists
  • Subscribe
  • User lists
    • pgsql-admin
    • pgsql-advocacy
    • pgsql-announce
    • pgsql-bugs
    • pgsql-docs
    • pgsql-general
    • pgsql-jobs
    • pgsql-novice
    • pgsql-performance
    • pgsql-php
    • pgsql-sql
    • pgsql-students
  • Developer lists
  • Regional lists
  • Associations
  • User groups
  • Project lists
  • Inactive lists
• IRC
• Featured Users
• International Sites
• Propaganda
• Resources
• Weekly News
• Community login
  • Profile
  • Lost password

pgsql-performance 2006-11 Thread Index (1/2)

• Main Index
• [Prev Page]
• [Next Page]

• Bad iostat numbers Carlos H. Reimer (Fri 01 00:44)
• Re: Bad iostat numbers Mark Kirkwood (Fri 01 01:47)
• Re: Bad iostat numbers David Boreham (Fri 01 02:24)
• Re: Bad iostat numbers Mark Kirkwood (Fri 01 03:00)
• Defining performance. Paul Lathrop (Thu 30 23:31)
• Re: Defining performance. Tobias Brox (Fri 01 00:05)
• Re: Defining performance. Jeff Davis (Fri 01 00:58)
• Re: Defining performance. Tobias Brox (Fri 01 01:08)
• Re: Defining performance. Tom Lane (Fri 01 00:26)
• Re: Defining performance. Scott Marlowe (Fri 01 00:44)
• <Possible follow-ups>
• Re: Defining performance. nospam (Fri 01 01:10)
• Re: Defining performance. Tobias Brox (Fri 01 01:16)
• Re: Defining performance. Chris (Fri 01 03:32)
• Fw: [GENERAL] Including unique users in huge data warehouse in Postgresql... Mark Jensen (Wed 29 19:43)
• Re: Fw: [GENERAL] Including unique users in huge data Luke Lonergan (Wed 29 21:55)
• OT - how to size/match multiple databases/apps for a single server Kevin Kempter (Wed 29 18:09)
• NAMEDATALEN and performance Alessandro Baretta (Wed 29 11:32)
• Re: NAMEDATALEN and performance Tom Lane (Wed 29 15:50)
• Re: BUG #2784: Performance serious degrades over a period of a month Bruno Wolff III (Tue 28 04:25)
• Re: BUG #2784: Performance serious degrades over a period Bill Moran (Tue 28 11:34)
• Plattform comparison (lies, damn lies and benchmarks) Guido Neitzer (Mon 27 08:09)
• When to vacuum a table? Joost Kraaijeveld (Sun 26 11:24)
• Re: When to vacuum a table? Marcelo Costa (Sun 26 12:43)
• Re: When to vacuum a table? Steinar H. Gunderson (Sun 26 13:30)
• Re: When to vacuum a table? Marcelo Costa (Sun 26 13:46)
• Re: When to vacuum a table? Rod Taylor (Sun 26 14:31)
• Re: When to vacuum a table? Andrew Sullivan (Sun 26 14:34)
• Re: When to vacuum a table? Craig A. James (Sun 26 16:28)
• Re: When to vacuum a table? Tom Lane (Sun 26 17:06)
• Re: When to vacuum a table? Joshua D. Drake (Sun 26 17:46)
• Re: When to vacuum a table? Jim C. Nasby (Mon 27 01:01)
• Re: When to vacuum a table? Kevin Grittner (Mon 27 18:59)
• Massive delete of rows, how to proceed? Arnau (Fri 24 19:26)
• Message not available
  • Massive delete of rows, how to proceed? Peter Childs (Sat 25 15:45)
• Re: Massive delete of rows, how to proceed? Merlin Moncure (Mon 27 08:44)
• <Possible follow-ups>
• Re: Massive delete of rows, how to proceed? andrew (Sun 26 01:26)
• TPC-H Benchmark Felipe Rondon Rocha (Fri 24 14:08)
• Re: TPC-H Benchmark Luke Lonergan (Fri 24 16:31)
• Postgres scalability and performance on windows Gopal (Thu 23 22:38)
• Re: Postgres scalability and performance on windows Heikki Linnakangas (Thu 23 22:51)
• Re: Postgres scalability and performance on windows Guido Neitzer (Fri 24 08:27)
• Re: Postgres scalability and performance on windows Frank Wiles (Fri 24 17:50)
• Re: Postgres scalability and performance on windows Gopal (Tue 28 12:27)
• Re: Postgres scalability and performance on windows Tom Lane (Tue 28 16:25)
• Re: Postgres scalability and performance on windows J. Andrew Rogers (Tue 28 16:51)
• <Possible follow-ups>
• Re: Postgres scalability and performance on windows Gopal (Fri 24 10:14)
• Re: Postgres scalability and performance on windows Tom Lane (Sat 25 00:10)
• Direct I/O issues Greg Smith (Thu 23 06:40)
• Re: Direct I/O issues Tom Lane (Thu 23 16:46)
• Re: Direct I/O issues Greg Smith (Thu 23 18:10)
• Re: Direct I/O issues Bruce Momjian (Fri 24 04:06)
• PostgreSQL underestimates sorting Markus Schaber (Wed 22 13:51)
• Re: PostgreSQL underestimates sorting Steinar H. Gunderson (Wed 22 13:58)
• Re: PostgreSQL underestimates sorting Markus Schaber (Wed 22 14:28)
• Re: PostgreSQL underestimates sorting Frank Wiles (Wed 22 17:11)
• Re: PostgreSQL underestimates sorting Markus Schaber (Wed 22 16:59)
• Re: PostgreSQL underestimates sorting Simon Riggs (Thu 23 15:20)
• Priority to a mission critical transaction Carlos H. Reimer (Wed 22 02:11)
• Re: Priority to a mission critical transaction Brad Nicholson (Thu 23 20:40)
• Re: Priority to a mission critical transaction Jim C. Nasby (Mon 27 00:52)
• RES: Priority to a mission critical transaction Carlos H. Reimer (Tue 28 19:01)
• Re: RES: Priority to a mission critical transaction Tom Lane (Tue 28 19:07)
• Re: RES: Priority to a mission critical transaction Bruce Momjian (Tue 28 23:44)
• Re: RES: Priority to a mission critical transaction Ron Mayer (Wed 29 01:20)
• Re: RES: Priority to a mission critical transaction Brian Hurt (Wed 29 13:26)
• Re: RES: Priority to a mission critical transaction Mark Lewis (Wed 29 15:03)
• Re: RES: Priority to a mission critical transaction Brian Hurt (Wed 29 15:17)
• Re: RES: Priority to a mission critical transaction Ron Mayer (Wed 29 16:43)
• Re: RES: Priority to a mission critical transaction Brian Hurt (Wed 29 17:21)
• Re: RES: Priority to a mission critical transaction Ron Mayer (Wed 29 18:47)
• Re: RES: Priority to a mission critical transaction Josh Berkus (Thu 30 04:29)
• Re: RES: Priority to a mission critical transaction Andreas Kostyrka (Tue 28 19:17)
• Re: RES: Priority to a mission critical transaction Josh Berkus (Tue 28 19:45)
• Re: RES: Priority to a mission critical transaction Mark Kirkwood (Wed 29 01:26)
• Re: RES: Priority to a mission critical transaction Ron Mayer (Tue 28 20:31)
• Re: RES: Priority to a mission critical transaction Mark Kirkwood (Wed 29 01:43)
• Re: RES: Priority to a mission critical transaction Ron Mayer (Wed 29 10:55)
• Slow Query Joe Lester (Tue 21 17:39)
• <Possible follow-ups>
• Re: Slow Query Joe Lester (Tue 21 20:28)
• BitMapScan performance degradation Jérôme BENOIS (Tue 21 14:45)
• Re: BitMapScan performance degradation Tom Lane (Tue 21 15:44)
• Re: BitMapScan performance degradation db (Tue 21 15:51)
• Re: BitMapScan performance degradation Jérôme BENOIS (Tue 21 17:01)
• start up cost estimate rakesh kumar (Sat 18 09:33)
• Re: start up cost estimate Joshua Marsh (Sat 18 14:27)
• Message not available
  • Fwd: start up cost estimate rakesh kumar (Sun 19 04:05)
• Re: start up cost estimate Tom Lane (Sat 18 18:11)
• Re: Optimicing Postgres for SunSolaris10 on V240 Josh Berkus (Fri 17 18:45)
• Re: Optimicing Postgres for SunSolaris10 on V240 Marc Cousin (Sat 18 10:09)
• availability of SATA vendors Jeff Frost (Fri 17 17:45)
• Re: availability of SATA vendors Arjen van der Meijden (Fri 17 19:20)
• Message not available
  • Re: availability of SATA vendors Ron (Fri 17 20:00)
• Re: availability of SATA vendors Steve Atkins (Fri 17 20:44)
• Re: availability of SATA vendors Luke Lonergan (Fri 17 21:54)
• Re: availability of SATA vendors Jeff Frost (Wed 22 01:54)
• Re: availability of SATA vendors Joshua D. Drake (Wed 22 02:13)
• Re: availability of SATA vendors Jeff Frost (Wed 22 02:15)
• Re: availability of SATA vendors Joshua D. Drake (Wed 22 02:37)
• Re: availability of SATA vendors Bucky Jordan (Wed 22 14:18)
• Re: availability of SATA vendors Jeff Frost (Wed 22 16:36)
• Re: availability of SATA vendors Joshua D. Drake (Wed 22 17:00)
• Re: availability of SATA vendors Jeff Frost (Wed 22 17:02)
• Re: availability of SATA vendors Joshua D. Drake (Wed 22 17:10)
• Re: availability of SATA vendors Scott Marlowe (Wed 22 17:34)
• Re: availability of SATA vendors Jim C. Nasby (Sun 26 23:31)
• Re: availability of SATA vendors Arjen van der Meijden (Wed 22 17:07)
• Re: availability of SATA vendors Luke Lonergan (Wed 22 23:03)
• Re: availability of SATA vendors Arjen van der Meijden (Thu 23 08:40)
• Re: availability of SATA vendors Bucky Jordan (Wed 22 22:38)
• Re: availability of SATA vendors Jim C. Nasby (Sun 26 23:34)
• shared_buffers > 284263 on OS X Brian Wipf (Fri 17 00:33)
• Re: shared_buffers > 284263 on OS X Dave Cramer (Sat 18 16:17)
• Re: shared_buffers > 284263 on OS X Tom Lane (Sat 18 18:30)
• Re: shared_buffers > 284263 on OS X Brian Wipf (Sun 19 03:13)
• Re: shared_buffers > 284263 on OS X Guido Neitzer (Sun 19 15:20)
• Re: shared_buffers > 284263 on OS X Jim C. Nasby (Sun 26 23:25)
• Re: shared_buffers > 284263 on OS X Brendan Duddridge (Mon 27 03:51)
• Re: shared_buffers > 284263 on OS X Tom Lane (Mon 27 04:04)
• Re: shared_buffers > 284263 on OS X Brian Wipf (Mon 27 04:11)
• Re: shared_buffers > 284263 on OS X Guido Neitzer (Mon 27 07:11)
• Re: shared_buffers > 284263 on OS X Guido Neitzer (Mon 27 07:35)
• Re: shared_buffers > 284263 on OS X Guido Neitzer (Mon 27 07:11)
• Re: shared_buffers > 284263 on OS X Brian Wipf (Mon 27 07:24)
• Re: shared_buffers > 284263 on OS X Jim C. Nasby (Mon 27 09:23)
• Re: shared_buffers > 284263 on OS X AgentM (Mon 27 16:05)
• Re: shared_buffers > 284263 on OS X Guido Neitzer (Mon 27 16:21)
• Re: shared_buffers > 284263 on OS X Guido Neitzer (Sat 18 18:48)
• Re: shared_buffers > 284263 on OS X Guido Neitzer (Sat 18 18:48)
• PostgreSQL with 64 bit was: Re: shared_buffers > 284263 on OS X Guido Neitzer (Sun 19 22:22)
• Postgres server crash Craig A. James (Thu 16 02:23)
• Re: Postgres server crash Russell Smith (Thu 16 02:28)
• Re: Postgres server crash Richard Huxton (Thu 16 10:46)
• Re: Postgres server crash Craig A. James (Thu 16 17:02)
• Re: Postgres server crash Richard Huxton (Thu 16 17:08)
• Re: Postgres server crash Tom Lane (Thu 16 18:14)
• Re: Postgres server crash Richard Troy (Sun 19 01:18)
• Re: Postgres server crash Craig A. James (Sun 19 06:45)
• Re: Postgres server crash Tom Lane (Sun 19 06:51)
• Re: Postgres server crash Ron Mayer (Sun 19 17:01)
• Re: Postgres server crash Ron Mayer (Sun 19 17:07)
• Re: Postgres server crash Mattias Kregert (Mon 20 22:58)
• Re: Postgres server crash Michael Stone (Sun 19 19:41)
• Re: Postgres server crash Richard Broersma Jr (Sun 19 20:42)
• Re: Postgres server crash Michael Stone (Sun 19 21:25)
• Re: Postgres server crash Craig A. James (Sun 19 22:13)
• Re: Postgres server crash Michael Stone (Sun 19 22:32)
• Re: Postgres server crash Craig A. James (Mon 20 01:02)
• Re: Postgres server crash Bruno Wolff III (Mon 20 01:59)
• Re: Postgres server crash Craig A. James (Mon 20 06:43)
• Re: Postgres server crash Markus Schaber (Tue 21 14:08)
• Re: Postgres server crash Jim C. Nasby (Sun 26 23:41)
• Re: Postgres server crash Michael Stone (Mon 27 13:20)
• Re: Postgres server crash Florian Weimer (Mon 27 18:33)
• Re: Postgres server crash Ben (Thu 16 20:51)
• Re: Postgres server crash Craig A. James (Thu 16 17:17)
• Re: Postgres server crash Richard Huxton (Thu 16 17:27)
• Re: Postgres server crash Tom Lane (Thu 16 18:10)
• Message not available
• Re: Postgres server crash Richard Huxton (Thu 16 18:19)
• Re: Postgres server crash Merlin Moncure (Thu 16 18:26)
• Hundreds of database and FSM Craig A. James (Wed 15 16:38)
• Re: Hundreds of database and FSM Alvaro Herrera (Wed 15 17:31)
• Re: Hundreds of database and FSM Steinar H. Gunderson (Wed 15 17:43)
• Slow SELECT on three or more clients AMIR FRANCO D. JOVEN (Wed 15 11:44)
• Re: Slow SELECT on three or more clients Andreas Kostyrka (Wed 15 13:26)
• Re: Slow SELECT on three or more clients Russell Smith (Wed 15 13:32)
• Re: Slow SELECT on three or more clients Gregory S. Williamson (Wed 15 13:59)
• Re: Slow SELECT on three or more clients Merlin Moncure (Wed 15 14:17)
• Re: Slow SELECT on three or more clients Markus Schaber (Wed 15 14:47)
• Re: Slow SELECT on three or more clients AMIR FRANCO D. JOVEN (Thu 16 08:54)
• Re: [BUGS] BUG #2737: hash indexing large table fails, while btree of same index works Tom Lane (Fri 10 23:55)
• Re: [BUGS] BUG #2737: hash indexing large table fails,while btree of same index works Simon Riggs (Sat 11 08:18)
• Re: [BUGS] BUG #2737: hash indexing large table fails,while btree of same index works Tom Lane (Thu 16 22:48)
• Re: [BUGS] BUG #2737: hash indexing large tablefails,while btree of same index works Simon Riggs (Fri 17 10:59)
• Message not available
  • Re: [BUGS] BUG #2737: hash indexing largetablefails,while btree of same index works Simon Riggs (Fri 17 14:38)
• Re: [BUGS] BUG #2737: hash indexing large tablefails,while btree of same index works Tom Lane (Fri 17 15:08)
• Re: [BUGS] BUG #2737: hash indexing large tablefails,while Julius.Stroffek (Fri 17 15:36)
• Lying drives [Was: Re: Which OS provides the _fastest_ PostgreSQL performance?] Ron Mayer (Fri 10 18:54)
• Re: Lying drives [Was: Re: Which OS provides the _fastest_ PostgreSQL performance?] Guy Thornley (Mon 13 09:01)
• Re: Lying drives [Was: Re: Which OS provides the _fastest_ Greg Smith (Thu 23 07:31)
• Re: Lying drives [Was: Re: Which OS provides the Bruce Momjian (Thu 23 16:44)

---

• Main Index
• [Prev Page]
• [Next Page]

---

Mail converted by MHonArc