Home > mailing lists

Mailing lists [pgsql-performance]

1 August 2008

01:27 Re: SSD Performance Article Scott Marlowe
08:31 Nls sorting in Postgresql-8.3.3 Praveen
08:43 Re: Nls sorting in Postgresql-8.3.3 Richard Huxton
11:03 Re: Database size Vs performance degradation Matthew Wakeling

3 August 2008

23:58 Re: Database size Vs performance degradation Fernando Ike

4 August 2008

11:25 Re: SSD Performance Article H. Hall
18:26 Re: Posible planner improvement? Kevin Grittner

5 August 2008

04:54 file system and raid performance Mark Wong
05:04 Re: file system and raid performance david@lang.hm
12:12 Re: file system and raid performance Gregory S. Youngblood
14:58 Re: file system and raid performance Mark Wong
15:00 Re: file system and raid performance Mark Wong
16:51 Re: file system and raid performance Fernando Ike

6 August 2008

00:04 Re: file system and raid performance Gregory S. Youngblood
00:12 Re: file system and raid performance Mark Kirkwood
10:21 pg_dump error - out of memory, Failed on request of size 536870912 Marcin Citowicki
10:26 Re: pg_dump error - out of memory, Failed on request of size 536870912 Marcin Citowicki
12:21 Re: pg_dump error - out of memory, Failed on request of size 536870912 Pavel Stehule
12:32 Re: pg_dump error - out of memory, Failed on request of size 536870912 Stefan Kaltenbrunner
21:35 query planner not using the correct index Joshua Shanks
22:19 Plz Heeeelp! performance settings dforum

7 August 2008

00:03 Re: file system and raid performance Mark Kirkwood
02:16 Re: Plz Heeeelp! performance settings Merlin Moncure
02:48 Re: query planner not using the correct index Craig Ringer
03:16 Re: query planner not using the correct index Joshua Shanks
03:26 Re: query planner not using the correct index Craig Ringer
06:09 Unexpectedly Long DELETE Wait Volkan YAZICI
07:35 Re: Plz Heeeelp! performance settings dforum
07:50 Query Plan choice with timestamps Giorgio Valoti
07:58 Re: Unexpectedly Long DELETE Wait Richard Huxton
08:34 Re: Plz Heeeelp! performance settings Richard Huxton
08:36 Re: Query Plan choice with timestamps Richard Huxton
09:29 Re: Plz Heeeelp! performance settings dforums
09:41 Re: file system and raid performance Mark Kirkwood
09:46 Filesystem setup on new system Henrik
10:21 Re: file system and raid performance Mario Weilguni
10:40 Re: Plz Heeeelp! performance settings Richard Huxton
12:31 Re: Query Plan choice with timestamps Giorgio Valoti
12:36 Re: Query Plan choice with timestamps Richard Huxton
13:40 Re: Plz Heeeelp! performance settings dforums
14:13 Re: Plz Heeeelp! performance settings Richard Huxton
14:37 Re: Unexpectedly Long DELETE Wait Volkan YAZICI
15:02 Another index related question.... ries van Twisk
15:06 Re: Plz Heeeelp! performance settings Merlin Moncure
15:08 Re: Plz Heeeelp! performance settings Richard Huxton
15:11 Re: query planner not using the correct index Joshua Shanks
15:51 Re: Query Plan choice with timestamps Tom Lane
18:37 Re: Query Plan choice with timestamps Giorgio Valoti
18:42 Re: Query Plan choice with timestamps Giorgio Valoti
19:30 Re: Query Plan choice with timestamps Giorgio Valoti
19:36 Re: file system and raid performance Mark Wong
21:00 Re: file system and raid performance Andrej Ricnik-Bay
21:01 Re: Query Plan choice with timestamps Tom Lane
21:12 Re: query planner not using the correct index Tom Lane
21:30 Re: file system and raid performance Scott Marlowe
21:57 Re: file system and raid performance Andrej Ricnik-Bay
22:02 Re: file system and raid performance Gregory S. Youngblood
22:02 Re: query planner not using the correct index Joshua Shanks
22:13 Re: file system and raid performance Scott Marlowe
22:15 Re: file system and raid performance Mark Mielke
22:38 Re: query planner not using the correct index Gregory Stark
23:05 Re: query planner not using the correct index Joshua Shanks
23:48 Re: query planner not using the correct index Tom Lane
23:55 Re: query planner not using the correct index Joshua Shanks

8 August 2008

00:13 Re: query planner not using the correct index Tom Lane
05:39 Re: Query Plan choice with timestamps Giorgio Valoti
07:42 Restoration of datas dforums
07:56 Re: Restoration of datas Richard Huxton
14:44 Filesystem benchmarking for pg 8.3.3 server Henrik
14:51 Re: query planner not using the correct index Joshua Shanks
15:04 Re: Filesystem benchmarking for pg 8.3.3 server Luke Lonergan
15:11 Re: Filesystem benchmarking for pg 8.3.3 server Henrik
16:28 Re: file system and raid performance Mark Wong
16:33 Re: file system and raid performance Mark Wong
16:44 Re: Filesystem benchmarking for pg 8.3.3 server Mark Wong
16:56 Re: file system and raid performance Mark Wong
19:22 Re: Filesystem benchmarking for pg 8.3.3 server Henrik
20:48 Re: Filesystem benchmarking for pg 8.3.3 server Andrej Ricnik-Bay
21:13 Re: file system and raid performance Mark Wong
22:30 Re: file system and raid performance Greg Smith
22:42 Re: Filesystem setup on new system Greg Smith
22:47 Re: Filesystem benchmarking for pg 8.3.3 server Greg Smith

9 August 2008

02:23 Re: Filesystem benchmarking for pg 8.3.3 server david@lang.hm
06:21 Re: index scan cost Jeff Frost
17:29 Distant mirroring dforum
19:29 Re: Distant mirroring Scott Marlowe
20:39 why query plan for the inner SELECT of WHERE x IN is wrong, but when run the inner query alone is OK? Miernik
20:58 Re: why query plan for the inner SELECT of WHERE x IN is wrong, but when run the inner query alone is OK? Tom Lane
21:21 Re: why query plan for the inner SELECT of WHERE x IN is wrong, but when run the inner query alone is OK? Miernik
21:37 Re: why query plan for the inner SELECT of WHERE x IN is wrong, but when run the inner query alone is OK? Miernik
21:37 Re: why query plan for the inner SELECT of WHERE x IN is wrong, but when run the inner query alone is OK? Tom Lane
21:57 Re: why query plan for the inner SELECT of WHERE x IN is wrong, but when run the inner query alone is OK? Miernik
22:32 Re: why query plan for the inner SELECT of WHERE x IN is wrong, but when run the inner query alone is OK? Miernik

10 August 2008

02:39 Re: why query plan for the inner SELECT of WHERE x IN is wrong, but when run the inner query alone is OK? Miernik
03:30 Re: why query plan for the inner SELECT of WHERE x IN is wrong, but when run the inner query alone is OK? Scott Carey
19:41 Re: Filesystem benchmarking for pg 8.3.3 server Henrik

11 August 2008

07:02 Re: long transaction Sabin Coanda
08:04 Using PK value as a String Jay
09:18 Re: Filesystem benchmarking for pg 8.3.3 server Henrik
09:30 Re: Using PK value as a String Gregory Stark
09:46 Re: Using PK value as a String Valentin Bogdanov
10:17 答复: [PERFORM] Using PK value as a String jay
10:35 Re: Filesystem benchmarking for pg 8.3.3 server Glyn Astill
12:08 Re: Filesystem benchmarking for pg 8.3.3 server Henrik
12:22 Re: Using PK value as a String ries van Twisk
13:20 Re: Filesystem benchmarking for pg 8.3.3 server Scott Marlowe
14:37 Re: Distant mirroring dforums
14:51 Sven Clement
15:05 Re: Filesystem benchmarking for pg 8.3.3 server Jeff
15:35 Re: Distant mirroring Fernando Hevia
15:56 Re: Filesystem benchmarking for pg 8.3.3 server Greg Smith
16:00 Re: Distant mirroring Scott Marlowe
16:04 Re: Using PK value as a String Craig James
19:04 Re: long transaction Merlin Moncure

12 August 2008

08:32 Re: long transaction Sabin Coanda
09:58 Re: Using PK value as a String Mario Weilguni
10:18 Re: Using PK value as a String Jay D. Kang
12:51 Re: Using PK value as a String Gregory Stark
13:06 Re: Using PK value as a String Bill Moran
13:28 Re: Using PK value as a String Mark Mielke
13:47 Re: Using PK value as a String Gregory Stark
13:57 Re: Using PK value as a String Mathias Stjernström
14:19 Re: Using PK value as a String Mark Mielke
14:29 Re: Using PK value as a String Merlin Moncure
14:49 Re: Using PK value as a String Moritz Onken
15:04 Re: Using PK value as a String Bill Moran
15:10 Re: Using PK value as a String Moritz Onken
15:18 Re: Distant mirroring dforums
15:21 Re: Using PK value as a String Bill Moran
15:25 Re: Using PK value as a String Moritz Onken
15:36 Re: Using PK value as a String Steve Atkins
15:48 Re: Using PK value as a String Bill Moran
15:57 Re: Using PK value as a String Mark Mielke
16:56 Re: long transaction Merlin Moncure
18:52 Re: Using PK value as a String H. Hall
19:40 Re: Filesystem benchmarking for pg 8.3.3 server Henrik
20:42 Re: Filesystem benchmarking for pg 8.3.3 server Scott Marlowe
21:48 Re: Filesystem benchmarking for pg 8.3.3 server Ron Mayer
22:27 Incorrect estimates on correlated filters Chris Kratz

13 August 2008

00:44 Re: Filesystem benchmarking for pg 8.3.3 server Scott Carey
00:52 Re: Filesystem benchmarking for pg 8.3.3 server Ron Mayer
00:57 Re: Filesystem benchmarking for pg 8.3.3 server Scott Marlowe
01:32 Re: Filesystem benchmarking for pg 8.3.3 server david@lang.hm
02:59 Re: Filesystem benchmarking for pg 8.3.3 server Scott Carey
04:33 Re: Filesystem benchmarking for pg 8.3.3 server Ron Mayer
06:21 Re: Filesystem benchmarking for pg 8.3.3 server Greg Smith
06:33 Re: long transaction Sabin Coanda
07:03 Re: Filesystem benchmarking for pg 8.3.3 server Scott Marlowe
10:16 Re: Filesystem benchmarking for pg 8.3.3 server Matthew Wakeling
13:25 Re: Filesystem benchmarking for pg 8.3.3 server Ron Mayer
14:41 Re: Filesystem benchmarking for pg 8.3.3 server Ron Mayer
14:48 Re: Filesystem benchmarking for pg 8.3.3 server Scott Marlowe
15:45 Re: query plan, index scan cost Decibel!
15:46 Re: Filesystem benchmarking for pg 8.3.3 server Decibel!
15:46 Re: Incorrect estimates on correlated filters Decibel!
16:57 Re: Filesystem benchmarking for pg 8.3.3 server Greg Smith
18:52 Re: Incorrect estimates on correlated filters Chris Kratz
19:55 Re: Filesystem benchmarking for pg 8.3.3 server Henrik
20:58 Re: Incorrect estimates on correlated filters Alvaro Herrera
21:28 autovacuum: use case for indenpedent TOAST table autovac settings Alvaro Herrera
22:30 Re: Filesystem benchmarking for pg 8.3.3 server Ron Mayer

14 August 2008

00:53 Re: autovacuum: use case for indenpedent TOAST table autovac settings Tom Lane
01:28 Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings Alvaro Herrera
01:31 Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings Tom Lane
01:48 Re: Incorrect estimates on correlated filters Craig Ringer
09:43 Re: [HACKERS] autovacuum: use case for indenpedent TOAST table autovac settings Simon Riggs
10:12 Re: Incorrect estimates on correlated filters Gregory Stark
14:10 Re: Filesystem benchmarking for pg 8.3.3 server Greg Smith
14:54 Re: Filesystem benchmarking for pg 8.3.3 server Scott Marlowe
18:09 Experiences storing binary in Postgres juliano.freitas@ati.pe.gov.br

15 August 2008

04:39 Re: Filesystem benchmarking for pg 8.3.3 server Ron Mayer
18:36 Optimizing a VIEW Madison Kelly
19:23 Re: file system and raid performance Bruce Momjian
19:32 Re: file system and raid performance Mark Wong

16 August 2008

04:56 Re: file system and raid performance Greg Smith
15:01 Re: file system and raid performance Mark Mielke
21:52 Re: Incorrect estimates on correlated filters Decibel!
21:52 Re: Experiences storing binary in Postgres Decibel!
21:52 Re: Filesystem benchmarking for pg 8.3.3 server Decibel!
21:53 Re: Optimizing a VIEW Decibel!

17 August 2008

00:21 Re: Filesystem benchmarking for pg 8.3.3 server david@lang.hm
01:33 Re: Optimizing a VIEW Rodrigo E. De León Plicet
01:36 Re: Optimizing a VIEW Rodrigo E. De León Plicet
02:19 Re: Optimizing a VIEW Gurjeet Singh
10:55 Re: Filesystem benchmarking for pg 8.3.3 server Gregory Stark
11:18 Re: Filesystem benchmarking for pg 8.3.3 server Gregory Stark
15:21 Re: Optimizing a VIEW Madison Kelly

18 August 2008

00:05 Re: long transaction Merlin Moncure
11:06 Re: Optimizing a VIEW Matthew Wakeling
13:37 Cross Join Problem Gauri Kanekar
14:02 Re: Cross Join Problem Tom Lane
14:09 Slow query with a lot of data Moritz Onken
14:30 Re: Slow query with a lot of data Matthew Wakeling
14:43 Re: Slow query with a lot of data Moritz Onken
14:57 Re: Slow query with a lot of data Matthew Wakeling
15:20 Re: Cross Join Problem Tom Lane
15:33 Re: file system and raid performance Mark Wong
15:49 Re: Slow query with a lot of data Moritz Onken
16:05 Re: Slow query with a lot of data Matthew Wakeling

19 August 2008

09:03 Re: Slow query with a lot of data Moritz Onken
11:13 Re: Slow query with a lot of data Matthew Wakeling
11:39 Re: Slow query with a lot of data Moritz Onken
12:27 Re: Slow query with a lot of data Matthew Wakeling
12:47 Re: Slow query with a lot of data Moritz Onken
13:34 Re: Cross Join Problem Gauri Kanekar
14:56 Re: Slow query with a lot of data Scott Carey
15:28 Re: Slow query with a lot of data Moritz Onken

20 August 2008

05:23 Software vs. Hardware RAID Data Mark Wong
05:54 Re: Software vs. Hardware RAID Data david@lang.hm
07:53 Re: Software vs. Hardware RAID Data Tommy Gildseth
07:54 Re: Slow query with a lot of data Moritz Onken
09:10 Re: Slow query with a lot of data Zoltan Boszormenyi
09:22 Re: pgsql do not handle NULL constants in the view Sergey Hripchenko
09:23 pgsql do not handle NULL constants in the view Sergey Hripchenko
12:26 PostgreSQL+Hibernate Performance Kranti K K Parisa™
12:55 Re: pgsql do not handle NULL constants in the view Tom Lane
13:49 Re: pgsql do not handle NULL constants in the view Sergey Hripchenko
14:48 Re: PostgreSQL+Hibernate Performance Mark Lewis
15:03 Re: PostgreSQL+Hibernate Performance Kranti K K Parisa™
15:03 Re: Software vs. Hardware RAID Data Mark Wong
15:06 Re: PostgreSQL+Hibernate Performance Nikolas Everett
15:06 Re: Software vs. Hardware RAID Data Mark Wong
15:12 Re: PostgreSQL+Hibernate Performance Kranti K K Parisa™
15:24 Re: PostgreSQL+Hibernate Performance Matthew Wakeling
15:25 Re: PostgreSQL+Hibernate Performance Mark Lewis
15:29 Re: PostgreSQL+Hibernate Performance Mark Lewis
16:01 Re: Slow query with a lot of data Scott Carey
17:34 Re: Optimizing a VIEW Decibel!
17:35 Re: Optimizing a VIEW Decibel!
18:08 Re: Slow query with a lot of data Scott Carey
18:30 Re: Optimizing a VIEW Tom Lane
18:38 Re: Slow query with a lot of data Tom Lane
19:56 Postgres not using array André Volpato
20:16 Re: Postgres not using array David Wilson
20:46 Re: Postgres not using array André Volpato
22:54 How to setup disk spindles for best performance Christiaan Willemsen

21 August 2008

01:50 Re: How to setup disk spindles for best performance Merlin Moncure
05:34 Re: How to setup disk spindles for best performance Scott Marlowe
05:39 Re: How to setup disk spindles for best performance Christiaan Willemsen
05:50 Re: How to setup disk spindles for best performance Joshua D. Drake
06:59 Re: PostgreSQL+Hibernate Performance Kranti K K Parisa™
07:04 Re: PostgreSQL+Hibernate Performance Kranti K K Parisa™
07:04 Re: Slow query with a lot of data Moritz Onken
07:05 Re: Slow query with a lot of data Moritz Onken
07:45 Re: Slow query with a lot of data Moritz Onken
08:41 Re: How to setup disk spindles for best performance Christiaan Willemsen
13:57 Re: Postgres not using array André Volpato
14:02 Re: PostgreSQL+Hibernate Performance Mark Lewis
14:16 Re: Postgres not using array Mark Mielke
14:28 Re: Postgres not using array Tom Lane
14:39 Re: Slow query with a lot of data Scott Carey
14:51 Re: Postgres not using array André Volpato
15:00 Re: How to setup disk spindles for best performance Scott Carey
15:06 Re: How to setup disk spindles for best performance Christiaan Willemsen
15:08 Re: Slow query with a lot of data Moritz Onken
17:09 Re: Slow query with a lot of data Merlin Moncure
18:26 The state of PG replication in 2008/Q2? Dan Harris
19:10 Re: Postgres not using array Tom Lane
19:15 Re: How to setup disk spindles for best performance Ron Mayer
20:05 Re: Postgres not using array André Volpato
20:53 Re: The state of PG replication in 2008/Q2? Mathias Stjernström
21:04 Re: The state of PG replication in 2008/Q2? Andrew Sullivan
21:13 Re: The state of PG replication in 2008/Q2? Alan Hodgson
21:21 Re: The state of PG replication in 2008/Q2? Mathias Stjernström
21:23 Re: The state of PG replication in 2008/Q2? Joshua Drake
21:33 Re: The state of PG replication in 2008/Q2? salman
21:42 Re: The state of PG replication in 2008/Q2? Alan Hodgson
21:54 Re: The state of PG replication in 2008/Q2? Alvaro Herrera
22:10 Re: The state of PG replication in 2008/Q2? david@lang.hm
22:15 Re: The state of PG replication in 2008/Q2? Joshua Drake
22:50 Why do my hash joins turn to nested loops? pgsql-performance@ian.org

22 August 2008

01:08 Re: Why do my hash joins turn to nested loops? Tom Lane
05:52 Re: PostgreSQL+Hibernate Performance Kranti K K Parisa™
06:27 Re: The state of PG replication in 2008/Q2? RW
06:29 Re: The state of PG replication in 2008/Q2? Mathias Stjernström
06:32 Re: Slow query with a lot of data Moritz Onken
06:36 Re: The state of PG replication in 2008/Q2? Mathias Stjernström
09:41 Re: The state of PG replication in 2008/Q2? Peter Eisentraut
10:29 Re: Postgres not using array Gregory Stark
12:01 Identifying the nature of blocking I/O Peter Schuller
14:38 Re: The state of PG replication in 2008/Q2? Jan Otto
16:04 Nested Loop join being improperly chosen Brad Ediger
16:29 Re: Optimizing a VIEW Decibel!
17:06 Re: Postgres not using array André Volpato
17:57 Re: Slow query with a lot of data Merlin Moncure
18:33 Re: Why do my hash joins turn to nested loops? pgsql-performance@ian.org
20:37 Big delete on big table... now what? Fernando Hevia
21:31 Re: Big delete on big table... now what? Kevin Grittner
22:44 Re: Big delete on big table... now what? Bill Moran

23 August 2008

00:41 Re: Big delete on big table... now what? Gregory Stark
01:41 Large number of tables slow insert Loic Petit
07:40 Re: The state of PG replication in 2008/Q2? Shane Ambler
10:30 Re: Large number of tables slow insert DiezelMax
20:24 Re: Large number of tables slow insert tls.wydd@free.fr
20:27 Re: Large number of tables slow insert Loic Petit
23:50 Re: Large number of tables slow insert Scott Marlowe

24 August 2008

00:18 Re: Large number of tables slow insert tls.wydd@free.fr
00:26 Re: Large number of tables slow insert Scott Marlowe
00:47 Re: Large number of tables slow insert Loic Petit
00:50 Re: Large number of tables slow insert Scott Marlowe
00:59 Re: Large number of tables slow insert Loic Petit
01:18 Re: Large number of tables slow insert Scott Marlowe
01:31 Re: Large number of tables slow insert Loic Petit
01:37 Re: Large number of tables slow insert Scott Marlowe
01:48 Re: Large number of tables slow insert Loic Petit
14:42 Re: Large number of tables slow insert dforum
14:42 Re: Large number of tables slow insert DiezelMax
20:03 NOW vs CURRENT_DATE dforum
20:59 Re: Large number of tables slow insert Scott Carey
21:02 Re: Large number of tables slow insert H. Hall
21:22 Re: NOW vs CURRENT_DATE Peter Schuller
21:30 Re: Large number of tables slow insert Peter Schuller
22:30 Re: Large number of tables slow insert Loic Petit

25 August 2008

00:48 Re: Identifying the nature of blocking I/O Craig Ringer
01:15 Re: Large number of tables slow insert Scott Carey
01:34 Re: Identifying the nature of blocking I/O Scott Carey
01:37 Re: Identifying the nature of blocking I/O Tom Lane
01:50 Re: Identifying the nature of blocking I/O Tom Lane
02:22 Re: Large number of tables slow insert Loic Petit
02:30 Re: Identifying the nature of blocking I/O Alvaro Herrera
06:13 Re: NOW vs CURRENT_DATE Tino Wildenhain
08:18 Re: Identifying the nature of blocking I/O Alexander Staubo
08:32 Re: Identifying the nature of blocking I/O RW
13:37 Re: Big delete on big table... now what? Fernando Hevia
14:23 Re: Identifying the nature of blocking I/O Jonah H. Harris

26 August 2008

12:50 Re: Large number of tables slow insert Matthew Wakeling
15:30 Re: Large number of tables slow insert Scott Marlowe
16:10 Autovacuum does not stay turned off Jerry Champlin
16:14 Re: Autovacuum does not stay turned off hubert depesz lubaczewski
16:22 Re: Autovacuum does not stay turned off Andrew Sullivan
16:38 Query w empty result set with LIMIT orders of magnitude slower than without Frank Joerdens
16:44 select on 22 GB table causes "An I/O error occured while sending to the backend." exception henk de wit
16:46 Re: Autovacuum does not stay turned off Jerry Champlin
16:53 Re: Query w empty result set with LIMIT orders of magnitude slower than without Tom Lane
17:00 Re: Query w empty result set with LIMIT orders of magnitude slower than without (SOLVED, pls disregard) Frank Joerdens
17:04 Re: Autovacuum does not stay turned off hubert depesz lubaczewski
17:10 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Mark Lewis
18:06 Re: Autovacuum does not stay turned off Jerry Champlin
18:27 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe
18:42 Re: Query w empty result set with LIMIT orders of magnitude slower than without Frank Joerdens
20:31 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

27 August 2008

01:09 control the number of clog files and xlog files Duan Ligong
01:57 Re: control the number of clog files and xlog files Alvaro Herrera
07:21 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Florian Weimer
11:28 Re: control the number of clog files and xlog files Duan Ligong
13:01 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Bill Moran
13:09 Re: control the number of clog files and xlog files Alvaro Herrera
13:27 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception DANIEL CRISTIAN CRUZ
13:45 Is there a way to SubPartition? Jerry Champlin
14:04 Re: Is there a way to SubPartition? Tom Lane
14:10 Re: Is there a way to SubPartition? Matthew Wakeling
16:46 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Shane Ambler
20:21 Re: Is there a way to SubPartition? Jerry Champlin
20:32 Re: Is there a way to SubPartition? Alvaro Herrera
20:54 Re: Is there a way to SubPartition? Tom Lane
21:45 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
22:14 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Andrew Sullivan
22:21 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
22:29 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe

28 August 2008

02:20 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Alvaro Herrera
04:37 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
06:00 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Craig James
06:16 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
06:23 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
08:14 indexing for distinct search in timestamp based table Rainer Mager
09:46 Re: indexing for distinct search in timestamp based table H. Hall
12:36 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Andrew Sullivan
13:27 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling
13:54 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Bill Moran
14:50 Re: select on 22 GB table causes"An I/O error occured while sending to the backend." exception Kevin Grittner
15:07 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Steve Atkins
15:47 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Jerry Champlin
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 Matthew Wakeling
16:48 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
16:51 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
17:56 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Jeff Davis
18:14 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Craig James
18:18 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
18:27 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
18:33 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Jeff Davis
19:29 Best hardware/cost tradoff? cluster
19:31 update - which way quicker? Emi Lu
19:46 Re: Best hardware/cost tradoff? Scott Marlowe
20:04 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling
20:05 Re: Best hardware/cost tradoff? Fernando Hevia
20:09 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling
20:25 Re: Best hardware/cost tradoff? Craig James
20:29 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling
21:14 Re: update - which way quicker? paul socha
21:30 Re: Best hardware/cost tradoff? cluster
21:47 Re: Best hardware/cost tradoff? Scott Marlowe
22:03 Re: Best hardware/cost tradoff? Scott Marlowe
22:42 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe
22:48 Re: indexing for distinct search in timestamp based table David Rowley
23:01 Re: Nested Loop join being improperly chosen David Rowley
23:02 Re: indexing for distinct search in timestamp based table Scott Carey
23:08 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
23:23 Re: Nested Loop join being improperly chosen Brad Ediger

29 August 2008

01:11 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe
01:16 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
01:52 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe
01:53 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Dennis
02:02 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Scott Marlowe
02:29 Re: Postgres not using array Greg Smith
02:32 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Alvaro Herrera
02:42 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
02:44 Re: How to setup disk spindles for best performance Greg Smith
02:50 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Alvaro Herrera
03:06 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception david@lang.hm
03:55 Re: Identifying the nature of blocking I/O Greg Smith
04:41 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
05:08 Re: How to setup disk spindles for best performance Christiaan Willemsen
05:38 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception James Mansion
07:33 Re: indexing for distinct search in timestamp based table Rainer Mager
08:01 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Magnus Hagander
11:02 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling
11:09 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Bill Moran
11:22 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Gregory Williamson
13:48 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Alvaro Herrera
15:31 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Craig James
15:56 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Matthew Wakeling
16:16 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Greg Smith
16:22 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Valentin Bogdanov
16:38 Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception Gregory S. Youngblood

30 August 2008

10:30 Re: Best hardware/cost tradoff? cluster

31 August 2008

13:32 slow update of index during insert/copy Thomas Finneid
18:38 Re: slow update of index during insert/copy Scott Carey
19:20 Re: slow update of index during insert/copy Thomas Finneid