Home > mailing lists

Mailing lists [pgsql-performance]

1 February 2012

13:33 Index with all necessary columns - Postgres vs MSSQL Gudmundur Johannesson
13:52 Re: Index with all necessary columns - Postgres vs MSSQL Merlin Moncure
14:19 Re: From Simple to Complex Alessandro Gagliardi
14:32 Re: Index with all necessary columns - Postgres vs MSSQL Scott Marlowe
14:35 Re: From Simple to Complex Scott Marlowe
14:48 Re: From Simple to Complex Alessandro Gagliardi
14:53 Re: From Simple to Complex Scott Marlowe
15:05 Re: From Simple to Complex Bob Lunney
15:19 Re: From Simple to Complex Alessandro Gagliardi
15:35 Re: Index with all necessary columns - Postgres vs MSSQL Merlin Moncure

2 February 2012

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

3 February 2012

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

4 February 2012

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

5 February 2012

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

6 February 2012

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

7 February 2012

00:43 Re: How to improve insert speed with index on text column Saurabh
06:18 Inserts or Updates Ofer Israeli
08:27 Re: Inserts or Updates Kevin Grittner
10:47 Re: Inserts or Updates Andy Colson
11:12 Re: Index with all necessary columns - Postgres vs MSSQL Igor Neyman
13:28 Re: Inserts or Updates Ofer Israeli
13:31 Re: Inserts or Updates Claudio Freire
13:40 Re: Inserts or Updates Ofer Israeli
13:43 Re: Inserts or Updates Ofer Israeli
13:57 Re: Inserts or Updates Claudio Freire
15:12 Re: Inserts or Updates Ofer Israeli
15:21 Re: Inserts or Updates Claudio Freire
15:26 Re: Index with all necessary columns - Postgres vs MSSQL Merlin Moncure
15:30 Re: Inserts or Updates Andy Colson
15:41 Re: Inserts or Updates Kevin Grittner
15:43 Re: Inserts or Updates Andy Colson
21:00 random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
23:13 Re: how to demonstrate the effect of direct I/O ? Greg Smith

8 February 2012

03:31 index scan forward vs backward = speed difference of 357X slower! Kevin Traster
03:31 Re: Index with all necessary columns - Postgres vs MSSQL Gudmundur Johannesson
04:02 Re: index scan forward vs backward = speed difference of 357X slower! Rural Hunter
10:37 Re: index scan forward vs backward = speed difference of 357X slower! Rural Hunter
15:20 Re: Inserts or Updates Ofer Israeli
15:23 Re: Inserts or Updates Ofer Israeli
15:31 Re: index scan forward vs backward = speed difference of 357X slower! Tom Lane
15:34 Vacuuming problems on TOAST table Ofer Israeli
15:46 Re: Vacuuming problems on TOAST table Tom Lane
15:59 Re: index scan forward vs backward = speed difference of 357X slower! Kevin Traster
16:00 Re: Vacuuming problems on TOAST table Ofer Israeli
16:33 Re: pl/pgsql functions outperforming sql ones? Robert Haas
19:27 Re: index scan forward vs backward = speed difference of 357X slower! Merlin Moncure
19:32 Re: index scan forward vs backward = speed difference of 357X slower! Kevin Traster
19:41 Re: index scan forward vs backward = speed difference of 357X slower! Kevin Grittner
20:51 Re: random_page_cost = 2.0 on Heroku Postgres Josh Berkus
21:39 Re: random_page_cost = 2.0 on Heroku Postgres Scott Marlowe
21:46 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
22:28 Re: random_page_cost = 2.0 on Heroku Postgres Scott Marlowe
22:35 Re: random_page_cost = 2.0 on Heroku Postgres Marcos Ortiz Valmaseda
22:48 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
22:54 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg

9 February 2012

00:38 Re: random_page_cost = 2.0 on Heroku Postgres Scott Marlowe
00:40 Re: random_page_cost = 2.0 on Heroku Postgres Greg Sabino Mullane
01:42 Re: random_page_cost = 2.0 on Heroku Postgres Marcos Ortiz Valmaseda
06:10 Re: Inserts or Updates Vik Reykja
09:27 Re: Inserts or Updates Frank Lanitz
11:32 Re: random_page_cost = 2.0 on Heroku Postgres Jeff Janes
14:42 timestamp with time zone Alessandro Gagliardi
15:46 Re: timestamp with time zone Tom Lane
16:01 Re: timestamp with time zone Alessandro Gagliardi
16:15 Re: timestamp with time zone Kevin Grittner
16:38 Re: timestamp with time zone Alessandro Gagliardi
18:42 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
21:29 Re: random_page_cost = 2.0 on Heroku Postgres Scott Marlowe

10 February 2012

02:20 Re: timestamp with time zone Tom Lane
11:15 Performance on large, append-only tables David Yeu
11:20 Re: Performance on large, append-only tables Merlin Moncure
11:33 Re: Performance on large, append-only tables Claudio Freire
11:35 Re: Performance on large, append-only tables Marti Raudsepp
11:36 Re: Performance on large, append-only tables Tom Lane
11:44 Re: Performance on large, append-only tables Kevin Grittner
12:20 Re: Performance on large, append-only tables David Yeu
12:27 Re: Performance on large, append-only tables Claudio Freire
12:46 Re: Performance on large, append-only tables David Yeu
12:58 Re: Performance on large, append-only tables Claudio Freire
13:01 Re: Performance on large, append-only tables David Yeu
13:12 Re: Performance on large, append-only tables Claudio Freire
15:33 Re: random_page_cost = 2.0 on Heroku Postgres Josh Berkus
15:48 Re: random_page_cost = 2.0 on Heroku Postgres Cédric Villemain
15:54 Re: timestamp with time zone Alessandro Gagliardi
17:31 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
21:40 Re: random_page_cost = 2.0 on Heroku Postgres Josh Berkus
22:13 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg

11 February 2012

02:35 Re: rough benchmarks, sata vs. ssd CSS
12:26 Re: random_page_cost = 2.0 on Heroku Postgres Jeff Janes
15:53 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg

12 February 2012

06:49 Re: Inserts or Updates Ofer Israeli
14:29 Re: Inserts or Updates Frank Lanitz
14:32 Re: Inserts or Updates Ofer Israeli
15:49 Re: random_page_cost = 2.0 on Heroku Postgres Jeff Janes
16:02 Re: random_page_cost = 2.0 on Heroku Postgres Joshua Berkus
18:29 Re: random_page_cost = 2.0 on Heroku Postgres Peter van Hardenberg
19:37 Re: random_page_cost = 2.0 on Heroku Postgres Peter Geoghegan

13 February 2012

17:50 Re: rough benchmarks, sata vs. ssd CSS
18:12 Re: rough benchmarks, sata vs. ssd Ivan Voras

15 February 2012

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

16 February 2012

02:54 Re: Optimizer is not choosing index Markus Innerebner

17 February 2012

14:35 Why so slow? Alessandro Gagliardi
15:22 Re: Why so slow? Steve Crawford
18:20 Re: Why so slow? Alessandro Gagliardi

18 February 2012

01:29 Re: Why so slow? Ants Aasma
11:08 Query slow as Function Steve Horn
12:03 Re: Query slow as Function Andreas Kretschmer
12:37 Re: Query slow as Function Tom Lane
12:41 Re: Query slow as Function Andrew Dunstan
13:15 Re: Query slow as Function Steve Horn
13:20 Re: Query slow as Function Tom Lane
13:33 Re: Query slow as Function Andreas Kretschmer

20 February 2012

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

21 February 2012

13:59 Re: Indexes and Primary Keys on Rapidly Growing Tables Alessandro Gagliardi
19:53 Re: Indexes and Primary Keys on Rapidly Growing Tables Samuel Gendler
20:11 Re: Indexes and Primary Keys on Rapidly Growing Tables Alessandro Gagliardi

23 February 2012

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

24 February 2012

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

25 February 2012

15:18 Re: Very long deletion time on a 200 GB database Jeff Janes
20:16 PG as in-memory db? How to warm up and re-populate buffers? How to read in all tuples into memory? Stefan Keller
22: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

26 February 2012

03:34 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
04: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
06:47 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
06: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
07: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
09: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
10:17 Index condition in a Nested Loop Mark Hills
11: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
13:15 Re: : Cost calculation for EXPLAIN output Venkat Balaji
13:23 Re: : Cost calculation for EXPLAIN output Venkat Balaji
15: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
15: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
15: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
16: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
16: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
17:00 Re: Index condition in a Nested Loop Tom Lane
18: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

04:08 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
08: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
10:04 Joining tables by UUID field - very slow Cherio
10: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
10:04 Re: Very long deletion time on a 200 GB database lephongvu
10:46 Re: Very long deletion time on a 200 GB database Shaun Thomas
10:53 Re: Joining tables by UUID field - very slow Merlin Moncure
10:54 Re: Very long deletion time on a 200 GB database Andrew Dunstan
11:00 Re: Very long deletion time on a 200 GB database Reuven M. Lerner
11:01 Re: Very long deletion time on a 200 GB database Shaun Thomas
11:14 Re: Very long deletion time on a 200 GB database Shaun Thomas
11:25 Re: Joining tables by UUID field - very slow Tom Lane
15:01 Re: Very long deletion time on a 200 GB database Claudio Freire
17:14 Re: Very long deletion time on a 200 GB database Samuel Gendler
17:28 Re: Very long deletion time on a 200 GB database Scott Marlowe
17:55 Re: set autovacuum=off Filippos Kalamidas
18:00 Re: set autovacuum=off Filippos Kalamidas
19:14 Re: Index condition in a Nested Loop Mark Hills
20:17 Re: Index condition in a Nested Loop Tom Lane

28 February 2012

04: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
09: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
09: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
09: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
10: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
10: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
11: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
11: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
12: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
12: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
13:06 Re: Very long deletion time on a 200 GB database David Kerr
15:17 problems with set_config, work_mem, maintenance_work_mem, and sorting Jon Nelson
15:28 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Tom Lane
15:34 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Jon Nelson
16: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
16:52 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Tom Lane
17:38 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Jon Nelson
17:49 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Kääriäinen Anssi
17:55 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Tom Lane
18: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
18:47 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Claudio Freire
19:01 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Jon Nelson
19:43 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Claudio Freire
19: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

03:30 Re: problems with set_config, work_mem, maintenance_work_mem, and sorting Ants Aasma
06:16 Large insert and delete batches Anssi Kääriäinen
11: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
11: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
11: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
11: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
14:33 Re: text search: tablescan cost for a tsvector Robert Haas
14:35 Re: How to improve insert speed with index on text column Robert Haas
14:45 Re: Vacuuming problems on TOAST table Robert Haas
16:38 Performance of SQL Function versus View Igor Schtein
16:42 Re: text search: tablescan cost for a tsvector Marc Mamin
22:10 Re: Very long deletion time on a 200 GB database Lew
22:10 Re: Very long deletion time on a 200 GB database Gavin Flower
22:10 Inefficient min/max against partition (ver 9.1.1) McGehee, Robert