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

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

• 01 September 2008
  • Re: slow update of index during insert/copy Craig Ringer (01:49)
• 31 August 2008
  • Re: slow update of index during insert/copy Thomas Finneid (19:20)
  • Re: slow update of index during insert/copy Scott Carey (18:38)
  • slow update of index during insert/copy Thomas Finneid (13:32)
• 30 August 2008
  • Re: Best hardware/cost tradoff? cluster (10:30)
• 29 August 2008
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Gregory S. Youngblood (16:38)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Valentin Bogdanov (16:22)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Greg Smith (16:16)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling (15:56)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Craig James (15:31)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Alvaro Herrera (13:48)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Gregory Williamson (11:22)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Bill Moran (11:09)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling (11:02)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Magnus Hagander (08:01)
  • Re: indexing for distinct search in timestamp based table Rainer Mager (07:33)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception James Mansion (05:38)
  • Re: How to setup disk spindles for best performance Christiaan Willemsen (05:08)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Greg Smith (04:47)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Greg Smith (04:41)
  • Re: Identifying the nature of blocking I/O Greg Smith (03:55)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (03:06)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Alvaro Herrera (02:50)
  • Re: How to setup disk spindles for best performance Greg Smith (02:44)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (02:42)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Alvaro Herrera (02:32)
  • Re: Postgres not using array Greg Smith (02:29)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe (02:02)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Dennis (01:53)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe (01:52)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (01:16)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe (01:11)
• 28 August 2008
  • Re: Nested Loop join being improperly chosen Brad Ediger (23:23)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (23:08)
  • Re: indexing for distinct search in timestamp based table Scott Carey (23:02)
  • Re: Nested Loop join being improperly chosen David Rowley (23:01)
  • Re: indexing for distinct search in timestamp based table David Rowley (22:48)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe (22:42)
  • Re: Best hardware/cost tradoff? Scott Marlowe (22:03)
  • Re: Best hardware/cost tradoff? Scott Marlowe (21:47)
  • Re: Best hardware/cost tradoff? cluster (21:30)
  • Re: update - which way quicker? paul socha (21:14)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling (20:29)
  • Re: Best hardware/cost tradoff? Craig James (20:25)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling (20:09)
  • Re: Best hardware/cost tradoff? Fernando Hevia (20:05)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling (20:04)
  • Re: Best hardware/cost tradoff? Scott Marlowe (19:46)
  • update - which way quicker? Emi Lu (19:31)
  • Best hardware/cost tradoff? cluster (19:29)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Jeff Davis (18:33)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (18:27)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (18:18)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Craig James (18:14)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Jeff Davis (17:56)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (16:51)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (16:48)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling (16:03)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Craig James (16:03)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Jerry Champlin (15:47)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Steve Atkins (15:07)
  • Re: select on 22 GB table causes"An I/O error occured while sending to the backend." exception Kevin Grittner (14:50)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Bill Moran (13:54)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling (13:27)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Andrew Sullivan (12:36)
  • Re: indexing for distinct search in timestamp based table H. Hall (09:46)
  • indexing for distinct search in timestamp based table Rainer Mager (08:14)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (06:23)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (06:16)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Craig James (06:00)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Tom Lane (04:57)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Tom Lane (04:37)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Alvaro Herrera (02:20)
• 27 August 2008
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe (22:29)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (22:21)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Andrew Sullivan (22:14)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david (21:45)
  • Re: Is there a way to SubPartition? Tom Lane (20:54)
  • Re: Is there a way to SubPartition? Alvaro Herrera (20:32)
  • Re: Is there a way to SubPartition? Jerry Champlin (20:21)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Shane Ambler (16:46)
  • Re: Is there a way to SubPartition? Matthew Wakeling (14:10)
  • Re: Is there a way to SubPartition? Tom Lane (14:04)
  • Is there a way to SubPartition? Jerry Champlin (13:45)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception DANIEL CRISTIAN CRUZ (13:27)
  • Re: control the number of clog files and xlog files Alvaro Herrera (13:09)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Bill Moran (13:01)
  • Re: control the number of clog files and xlog files Duan Ligong (11:28)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Florian Weimer (07:21)
  • Re: control the number of clog files and xlog files Alvaro Herrera (01:57)
  • control the number of clog files and xlog files Duan Ligong (01:09)
• 26 August 2008
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception henk de wit (20:53)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception henk de wit (20:31)
  • Re: Query w empty result set with LIMIT orders of magnitude slower than without Frank Joerdens (18:42)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe (18:27)
  • Re: Autovacuum does not stay turned off Jerry Champlin (18:06)
  • Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Mark Lewis (17:10)
  • Re: Autovacuum does not stay turned off hubert depesz lubaczewski (17:04)
  • Re: Query w empty result set with LIMIT orders of magnitude slower than without (SOLVED, pls disregard) Frank Joerdens (17:00)
  • Re: Query w empty result set with LIMIT orders of magnitude slower than without Tom Lane (16:53)
  • Re: Autovacuum does not stay turned off Jerry Champlin (16:46)
  • select on 22 GB table causes "An I/O error occured while sending to the backend." exception henk de wit (16:44)
  • Query w empty result set with LIMIT orders of magnitude slower than without Frank Joerdens (16:38)
  • Re: Autovacuum does not stay turned off Andrew Sullivan (16:22)
  • Re: Autovacuum does not stay turned off hubert depesz lubaczewski (16:14)
  • Autovacuum does not stay turned off Jerry Champlin (16:10)
  • Re: Large number of tables slow insert Scott Marlowe (15:30)
  • Re: Large number of tables slow insert Matthew Wakeling (12:50)
• 25 August 2008
  • Re: Identifying the nature of blocking I/O Jonah H. Harris (14:23)
  • Re: Big delete on big table... now what? Fernando Hevia (13:37)
  • Re: Identifying the nature of blocking I/O RW (08:32)
  • Re: Identifying the nature of blocking I/O Alexander Staubo (08:18)
  • Re: NOW vs CURRENT_DATE Tino Wildenhain (06:13)
  • Re: Identifying the nature of blocking I/O Alvaro Herrera (02:30)
  • Re: Large number of tables slow insert Loic Petit (02:22)
  • Re: Identifying the nature of blocking I/O Tom Lane (01:50)
  • Re: Identifying the nature of blocking I/O Tom Lane (01:37)
  • Re: Identifying the nature of blocking I/O Scott Carey (01:34)
  • Re: Large number of tables slow insert Scott Carey (01:15)
  • Re: Identifying the nature of blocking I/O Craig Ringer (00:48)
• 24 August 2008
  • Re: Large number of tables slow insert Loic Petit (22:30)
  • Re: Large number of tables slow insert Peter Schuller (21:30)
  • Re: NOW vs CURRENT_DATE Peter Schuller (21:22)
  • Re: Large number of tables slow insert H. Hall (21:02)
  • Re: Large number of tables slow insert Scott Carey (20:59)
  • NOW vs CURRENT_DATE dforum (20:03)
  • Re: Large number of tables slow insert DiezelMax (14:42)
  • Re: Large number of tables slow insert dforum (14:42)
  • Re: Large number of tables slow insert Loic Petit (01:48)
  • Re: Large number of tables slow insert Scott Marlowe (01:37)
  • Re: Large number of tables slow insert Loic Petit (01:31)
  • Re: Large number of tables slow insert Scott Marlowe (01:18)
  • Re: Large number of tables slow insert Loic Petit (00:59)
  • Re: Large number of tables slow insert Scott Marlowe (00:50)
  • Re: Large number of tables slow insert Loic Petit (00:47)
  • Re: Large number of tables slow insert Scott Marlowe (00:26)
  • Re: Large number of tables slow insert tls . wydd (00:18)
• 23 August 2008
  • Re: Large number of tables slow insert Scott Marlowe (23:50)
  • Re: Large number of tables slow insert Loic Petit (20:27)
  • Re: Large number of tables slow insert tls . wydd (20:24)
  • Re: Large number of tables slow insert DiezelMax (10:30)
  • Re: The state of PG replication in 2008/Q2? Shane Ambler (07:40)
  • Large number of tables slow insert Loic Petit (01:41)
  • Re: Big delete on big table... now what? Gregory Stark (00:41)
• 22 August 2008
  • Re: Big delete on big table... now what? Bill Moran (22:44)
  • Re: Big delete on big table... now what? Kevin Grittner (21:31)
  • Big delete on big table... now what? Fernando Hevia (20:37)
  • Re: Why do my hash joins turn to nested loops? pgsql-performance (18:33)
  • Re: Slow query with a lot of data Merlin Moncure (17:57)
  • Re: Postgres not using array André Volpato (17:06)
  • Re: Optimizing a VIEW Decibel! (16:29)
  • Nested Loop join being improperly chosen Brad Ediger (16:04)
  • Re: The state of PG replication in 2008/Q2? Jan Otto (14:38)
  • Identifying the nature of blocking I/O Peter Schuller (12:01)
  • Re: Postgres not using array Gregory Stark (10:29)
  • Re: The state of PG replication in 2008/Q2? Peter Eisentraut (09:41)
  • Re: The state of PG replication in 2008/Q2? Mathias Stjernström (06:35)
  • Re: Slow query with a lot of data Moritz Onken (06:32)
  • Re: The state of PG replication in 2008/Q2? Mathias Stjernström (06:29)
  • Re: The state of PG replication in 2008/Q2? RW (06:27)
  • Re: PostgreSQL+Hibernate Performance Kranti K K Parisa™ (05:52)
  • Re: Why do my hash joins turn to nested loops? Tom Lane (01:08)
• 21 August 2008
  • Why do my hash joins turn to nested loops? pgsql-performance (22:50)
  • Re: The state of PG replication in 2008/Q2? Joshua Drake (22:15)
  • Re: The state of PG replication in 2008/Q2? david (22:10)
  • Re: The state of PG replication in 2008/Q2? Alvaro Herrera (21:54)
  • Re: The state of PG replication in 2008/Q2? Alan Hodgson (21:42)
  • Re: The state of PG replication in 2008/Q2? salman (21:33)
  • Re: The state of PG replication in 2008/Q2? Joshua Drake (21:23)
  • Re: The state of PG replication in 2008/Q2? Mathias Stjernström (21:21)
  • Re: The state of PG replication in 2008/Q2? Alan Hodgson (21:13)
  • Re: The state of PG replication in 2008/Q2? Andrew Sullivan (21:04)
  • Re: The state of PG replication in 2008/Q2? Mathias Stjernström (20:53)
  • Re: Postgres not using array André Volpato (20:05)
  • Re: How to setup disk spindles for best performance Ron Mayer (19:15)
  • Re: Postgres not using array Tom Lane (19:10)
  • The state of PG replication in 2008/Q2? Dan Harris (18:26)
  • Re: Slow query with a lot of data Merlin Moncure (17:09)
  • Re: Slow query with a lot of data Moritz Onken (15:08)
  • Re: How to setup disk spindles for best performance Christiaan Willemsen (15:06)

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