Home > mailing lists

Mailing lists [pgsql-performance]

1 February 2012

01:12 Re: How to improve insert speed with index on text column Jeff Janes
02:29 Re: How to improve insert speed with index on text column Rosser Schwarz
02:49 Re: How to improve insert speed with index on text column Claudio Freire
02:51 Re: How to improve insert speed with index on text column Claudio Freire
16:33 Index with all necessary columns - Postgres vs MSSQL Gudmundur Johannesson
16:52 Re: Index with all necessary columns - Postgres vs MSSQL Merlin Moncure
17:19 Re: From Simple to Complex Alessandro Gagliardi
17:32 Re: Index with all necessary columns - Postgres vs MSSQL Scott Marlowe
17:35 Re: From Simple to Complex Scott Marlowe
17:48 Re: From Simple to Complex Alessandro Gagliardi
17:53 Re: From Simple to Complex Scott Marlowe
18:05 Re: From Simple to Complex Bob Lunney
18:19 Re: From Simple to Complex Alessandro Gagliardi
18:35 Re: Index with all necessary columns - Postgres vs MSSQL Merlin Moncure

2 February 2012

13:52 Re: From Simple to Complex Merlin Moncure
16:41 *really* bad insert performance on table with unique index Jon Nelson
18:38 Re: From Simple to Complex Alessandro Gagliardi
19:31 Re: Index with all necessary columns - Postgres vs MSSQL Merlin Moncure
19:59 Re: *really* bad insert performance on table with unique index Jeff Janes

3 February 2012

10:23 Re: rough benchmarks, sata vs. ssd Ivan Voras
16:15 Re: Slow nested loop execution on larger server Robert Haas
17:48 Re: wal_level=archive gives better performance than minimal - why? Robert Haas
18:03 Re: How to improve insert speed with index on text column Kevin Grittner
19:54 Re: How to improve insert speed with index on text column Scott Marlowe
20:56 Re: How to remove a table statistics ? Robert Haas

4 February 2012

15:05 Re: wal_level=archive gives better performance than minimal - why? Cédric Villemain
15:20 Re: wal_level=archive gives better performance than minimal - why? Tomas Vondra
22:25 how to demonstrate the effect of direct I/O ? Tomas Vondra
22:34 Re: how to demonstrate the effect of direct I/O ? Tomas Vondra

5 February 2012

23:33 Re: Index with all necessary columns - Postgres vs MSSQL Gudmundur Johannesson
23:33 Re: Index with all necessary columns - Postgres vs MSSQL Gudmundur Johannesson
23:33 Re: Index with all necessary columns - Postgres vs MSSQL Gudmundur Johannesson

6 February 2012

10:05 text search: tablescan cost for a tsvector Marc Mamin

7 February 2012

03:43 Re: How to improve insert speed with index on text column Saurabh
09:18 Inserts or Updates Ofer Israeli
11:27 Re: Inserts or Updates Kevin Grittner
13:47 Re: Inserts or Updates Andy Colson
14:12 Re: Index with all necessary columns - Postgres vs MSSQL Igor Neyman
16:28 Re: Inserts or Updates Ofer Israeli
16:31 Re: Inserts or Updates Claudio Freire
16:40 Re: Inserts or Updates Ofer Israeli
16:43 Re: Inserts or Updates Ofer Israeli
16:57 Re: Inserts or Updates Claudio Freire
18:12 Re: Inserts or Updates Ofer Israeli
18:21 Re: Inserts or Updates Claudio Freire
18:26 Re: Index with all necessary columns - Postgres vs MSSQL Merlin Moncure
18:30 Re: Inserts or Updates Andy Colson
18:41 Re: Inserts or Updates Kevin Grittner
18:43 Re: Inserts or Updates Andy Colson

8 February 2012

00:00 random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
02:13 Re: how to demonstrate the effect of direct I/O ? Greg Smith
06:31 index scan forward vs backward = speed difference of 357X slower! Kevin Traster
06:31 Re: Index with all necessary columns - Postgres vs MSSQL Gudmundur Johannesson
07:02 Re: index scan forward vs backward = speed difference of 357X slower! Rural Hunter
13:37 Re: index scan forward vs backward = speed difference of 357X slower! Rural Hunter
18:20 Re: Inserts or Updates Ofer Israeli
18:23 Re: Inserts or Updates Ofer Israeli
18:31 Re: index scan forward vs backward = speed difference of 357X slower! Tom Lane
18:34 Vacuuming problems on TOAST table Ofer Israeli
18:46 Re: Vacuuming problems on TOAST table Tom Lane
18:59 Re: index scan forward vs backward = speed difference of 357X slower! Kevin Traster
19:00 Re: Vacuuming problems on TOAST table Ofer Israeli
19:33 Re: pl/pgsql functions outperforming sql ones? Robert Haas
22:27 Re: index scan forward vs backward = speed difference of 357X slower! Merlin Moncure
22:32 Re: index scan forward vs backward = speed difference of 357X slower! Kevin Traster
22:41 Re: index scan forward vs backward = speed difference of 357X slower! Kevin Grittner
23:51 Re: random_page_cost = 2.0 on Heroku Postgres Josh Berkus

9 February 2012

00:39 Re: random_page_cost = 2.0 on Heroku Postgres Scott Marlowe
00:46 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
01:28 Re: random_page_cost = 2.0 on Heroku Postgres Scott Marlowe
01:35 Re: random_page_cost = 2.0 on Heroku Postgres Marcos Ortiz Valmaseda
01:48 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
01:54 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
03:38 Re: random_page_cost = 2.0 on Heroku Postgres Scott Marlowe
03:40 Re: random_page_cost = 2.0 on Heroku Postgres Greg Sabino Mullane
04:42 Re: random_page_cost = 2.0 on Heroku Postgres Marcos Ortiz Valmaseda
09:10 Re: Inserts or Updates Vik Reykja
12:27 Re: Inserts or Updates Frank Lanitz
14:32 Re: random_page_cost = 2.0 on Heroku Postgres Jeff Janes
17:42 timestamp with time zone Alessandro Gagliardi
18:46 Re: timestamp with time zone Tom Lane
19:01 Re: timestamp with time zone Alessandro Gagliardi
19:15 Re: timestamp with time zone Kevin Grittner
19:38 Re: timestamp with time zone Alessandro Gagliardi
21:42 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg

10 February 2012

00:29 Re: random_page_cost = 2.0 on Heroku Postgres Scott Marlowe
05:20 Re: timestamp with time zone Tom Lane
14:15 Performance on large, append-only tables David Yeu
14:20 Re: Performance on large, append-only tables Merlin Moncure
14:33 Re: Performance on large, append-only tables Claudio Freire
14:35 Re: Performance on large, append-only tables Marti Raudsepp
14:36 Re: Performance on large, append-only tables Tom Lane
14:44 Re: Performance on large, append-only tables Kevin Grittner
15:20 Re: Performance on large, append-only tables David Yeu
15:27 Re: Performance on large, append-only tables Claudio Freire
15:46 Re: Performance on large, append-only tables David Yeu
15:58 Re: Performance on large, append-only tables Claudio Freire
16:01 Re: Performance on large, append-only tables David Yeu
16:12 Re: Performance on large, append-only tables Claudio Freire
18:33 Re: random_page_cost = 2.0 on Heroku Postgres Josh Berkus
18:48 Re: random_page_cost = 2.0 on Heroku Postgres Cédric Villemain
18:54 Re: timestamp with time zone Alessandro Gagliardi
20:31 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg

11 February 2012

00:40 Re: random_page_cost = 2.0 on Heroku Postgres Josh Berkus
01:13 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
05:35 Re: rough benchmarks, sata vs. ssd CSS
15:26 Re: random_page_cost = 2.0 on Heroku Postgres Jeff Janes
18:53 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg

12 February 2012

09:49 Re: Inserts or Updates Ofer Israeli
17:29 Re: Inserts or Updates Frank Lanitz
17:32 Re: Inserts or Updates Ofer Israeli
18:49 Re: random_page_cost = 2.0 on Heroku Postgres Jeff Janes
19:02 Re: random_page_cost = 2.0 on Heroku Postgres Joshua Berkus
21:29 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
22:37 Re: random_page_cost = 2.0 on Heroku Postgres Peter Geoghegan

13 February 2012

20:50 Re: rough benchmarks, sata vs. ssd CSS
21:12 Re: rough benchmarks, sata vs. ssd Ivan Voras

15 February 2012

09:19 Fwd: [HACKERS] client performance v.s. server statistics Zhou Han
09:55 Re: Fwd: [HACKERS] client performance v.s. server statistics Andres Freund
10:03 Re: Fwd: [HACKERS] client performance v.s. server statistics Han Zhou
10:33 Re: Fwd: [HACKERS] client performance v.s. server statistics Han Zhou
10:36 Re: Fwd: [HACKERS] client performance v.s. server statistics Andres Freund
17:34 UPDATE on NOT JOIN Gabriel Biberian
17:54 Fwd: [HACKERS] client performance v.s. server statistics Zhou Han
18:12 Re: UPDATE on NOT JOIN Marti Raudsepp
21:40 Optimizer is not choosing index Markus Innerebner
22:11 Re: Optimizer is not choosing index Tom Lane

16 February 2012

00:45 Re: Fwd: [HACKERS] client performance v.s. server statistics Han Zhou
05:54 Re: Optimizer is not choosing index Markus Innerebner

17 February 2012

17:35 Why so slow? Alessandro Gagliardi
18:22 Re: Why so slow? Steve Crawford
21:20 Re: Why so slow? Alessandro Gagliardi

18 February 2012

04:29 Re: Why so slow? Ants Aasma
14:08 Query slow as Function Steve Horn
15:03 Re: Query slow as Function Andreas Kretschmer
15:37 Re: Query slow as Function Tom Lane
15:41 Re: Query slow as Function Andrew Dunstan
16:15 Re: Query slow as Function Steve Horn
16:20 Re: Query slow as Function Tom Lane
16:33 Re: Query slow as Function Andreas Kretschmer

20 February 2012

06:24 Query slow as function Steve Horn
16:32 Re: Query slow as function Merlin Moncure
17:59 Insertions slower than Updates? Ofer Israeli
18:13 Re: Insertions slower than Updates? Kevin Grittner
18:21 Re: Insertions slower than Updates? Ofer Israeli
18:30 Re: Insertions slower than Updates? Kevin Grittner
18:32 Re: Insertions slower than Updates? Steve Horn
19:17 Re: Insertions slower than Updates? Ofer Israeli
19:17 Re: Insertions slower than Updates? Ofer Israeli
20:14 Re: Why so slow? Alessandro Gagliardi
21:06 Indexes and Primary Keys on Rapidly Growing Tables Alessandro Gagliardi
22:30 Re: Indexes and Primary Keys on Rapidly Growing Tables Josh Berkus

21 February 2012

16:59 Re: Indexes and Primary Keys on Rapidly Growing Tables Alessandro Gagliardi
22:53 Re: Indexes and Primary Keys on Rapidly Growing Tables Samuel Gendler
23:11 Re: Indexes and Primary Keys on Rapidly Growing Tables Alessandro Gagliardi

23 February 2012

07:40 Very long deletion time on a 200 GB database Reuven M. Lerner
08:50 Re: Very long deletion time on a 200 GB database Glyn Astill
09:08 Re: Very long deletion time on a 200 GB database Marcin Mańk
10:23 Re: Very long deletion time on a 200 GB database Richard Huxton
11:21 : Cost calculation for EXPLAIN output Venkat Balaji
11:23 set autovacuum=off Alessandro Gagliardi
11:35 Re: set autovacuum=off Thom Brown
13:07 Re: Very long deletion time on a 200 GB database Claudio Freire
13:25 Re: Very long deletion time on a 200 GB database Andrew Dunstan
14:18 Re: set autovacuum=off Andy Colson
14:26 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
14:29 Re: Very long deletion time on a 200 GB database ktm@rice.edu
14:47 Re: Very long deletion time on a 200 GB database Steve Crawford
15:37 Re: Very long deletion time on a 200 GB database Shaun Thomas
15:52 Re: : Cost calculation for EXPLAIN output Kevin Grittner
15:56 Re: : Cost calculation for EXPLAIN output Shaun Thomas
16:35 Re: set autovacuum=off Alessandro Gagliardi
16:46 Re: set autovacuum=off Thom Brown
16:56 Re: Very long deletion time on a 200 GB database Greg Spiegelberg
16:58 Re: set autovacuum=off Alessandro Gagliardi
17:01 Re: set autovacuum=off Steve Crawford
17:05 Re: Very long deletion time on a 200 GB database Shaun Thomas
17:11 Re: Very long deletion time on a 200 GB database Andy Colson
17:13 Re: Very long deletion time on a 200 GB database Greg Spiegelberg
17:31 Re: Very long deletion time on a 200 GB database Tom Lane
17:38 Re: set autovacuum=off Alessandro Gagliardi
17:42 Re: set autovacuum=off Peter van Hardenberg
18:04 Re: Very long deletion time on a 200 GB database Tom Lane
18:07 Re: set autovacuum=off Andy Colson
18:27 Re: set autovacuum=off Steve Crawford
18:48 Re: Very long deletion time on a 200 GB database Jesper Krogh
19:14 Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8 Jayashankar K B
19:20 Re: Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8 Tom Lane
19:28 Re: set autovacuum=off Alessandro Gagliardi
19:41 Re: set autovacuum=off Alessandro Gagliardi
19:57 Re: set autovacuum=off Andy Colson
20:08 Re: set autovacuum=off Alessandro Gagliardi
20:38 Re: set autovacuum=off Steve Crawford
21:30 Re: set autovacuum=off Alessandro Gagliardi
21:54 Re: set autovacuum=off Alessandro Gagliardi

24 February 2012

05:40 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
07:18 Re: Very long deletion time on a 200 GB database Lew
07:18 Re: set autovacuum=off Peter van Hardenberg
07:22 Re: Very long deletion time on a 200 GB database Samuel Gendler
11:38 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
12:07 Re: Very long deletion time on a 200 GB database Claudio Freire
13:34 Re: Very long deletion time on a 200 GB database Shaun Thomas
13:54 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
14:17 Re: Very long deletion time on a 200 GB database Shaun Thomas
16:20 Re: Very long deletion time on a 200 GB database Steve Crawford

25 February 2012

18:18 Re: Very long deletion time on a 200 GB database Jeff Janes
23:16 PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stefan Keller

26 February 2012

01:14 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Jeff Janes
06:34 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
07:52 Re： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Wales Wang
09:47 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
09:56 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stefan Keller
10:46 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Thomas Kellerer
12:55 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stephen Frost
13:17 Index condition in a Nested Loop Mark Hills
14:21 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Andy Colson
16:15 Re: : Cost calculation for EXPLAIN output Venkat Balaji
16:23 Re: : Cost calculation for EXPLAIN output Venkat Balaji
18:11 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stefan Keller
18:21 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Andy Colson
18:36 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Cédric Villemain
19:38 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stefan Keller
19:56 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stefan Keller
20:00 Re: Index condition in a Nested Loop Tom Lane
21:34 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Jeff Janes

27 February 2012

07:08 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
11:46 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Wales Wang
13:04 Joining tables by UUID field - very slow Cherio
13:04 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Cédric Villemain
13:04 Re: Very long deletion time on a 200 GB database lephongvu
13:46 Re: Very long deletion time on a 200 GB database Shaun Thomas
13:53 Re: Joining tables by UUID field - very slow Merlin Moncure
13:54 Re: Very long deletion time on a 200 GB database Andrew Dunstan
14:00 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
14:01 Re: Very long deletion time on a 200 GB database Shaun Thomas
14:14 Re: Very long deletion time on a 200 GB database Shaun Thomas
14:25 Re: Joining tables by UUID field - very slow Tom Lane
18:01 Re: Very long deletion time on a 200 GB database Claudio Freire
20:14 Re: Very long deletion time on a 200 GB database Samuel Gendler
20:28 Re: Very long deletion time on a 200 GB database Scott Marlowe
20:55 Re: set autovacuum=off Filippos Kalamidas
21:00 Re: set autovacuum=off Filippos Kalamidas
22:14 Re: Index condition in a Nested Loop Mark Hills
23:17 Re: Index condition in a Nested Loop Tom Lane

28 February 2012

07:31 Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stefan Keller
12:08 Re: [PERFORM] Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Claudio Freire
12:40 Re: [PERFORM] Re: [PERFORM] Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Tomas Vondra
12:52 Re: [PERFORM] Re: [PERFORM] Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Claudio Freire
13:16 Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Tomas Vondra
13:25 Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Claudio Freire
14:15 Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Jeff Janes
14:22 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Jeff Janes
15:05 Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Tomas Vondra
15:42 Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: [PERFORM] Re: 回复： [PERFORM] PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Claudio Freire
16:06 Re: Very long deletion time on a 200 GB database David Kerr
18:17 problems with set_config, work_mem, maintenance_work_mem, and sorting Jon Nelson
18:28 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Tom Lane
18:34 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Jon Nelson
19:49 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stefan Keller
19:52 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Tom Lane
20:38 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Jon Nelson
20:49 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Kääriäinen Anssi
20:55 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Tom Lane
21:41 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Claudio Freire
21:47 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Claudio Freire
22:01 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Jon Nelson
22:43 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Claudio Freire
22:46 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stefan Keller

29 February 2012

06:30 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Ants Aasma
09:16 Large insert and delete batches Anssi Kääriäinen
14:16 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Jeff Janes
14:18 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Claudio Freire
14:24 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stefan Keller
14:28 Re: PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stefan Keller
17:33 Re: text search: tablescan cost for a tsvector Robert Haas
17:35 Re: How to improve insert speed with index on text column Robert Haas
17:45 Re: Vacuuming problems on TOAST table Robert Haas
19:38 Performance of SQL Function versus View Igor Schtein
19:42 Re: text search: tablescan cost for a tsvector Marc Mamin