Discussion of PostgreSQL's performance issues. Please see Guide to reporting problems and Slow Query Questions for some tips on how to write your performance question.
Thread | Author | Time |
---|---|---|
select query does not pick up the right index | Abadie Lana | 16:28 |
Re: select query does not pick up the right index | Justin Pryzby | 16:45 |
Thread | Author | Time |
---|---|---|
Re: select query does not pick up the right index | David Rowley | 00:15 |
RE: select query does not pick up the right index | Abadie Lana | 12:57 |
RE: select query does not pick up the right index | Abadie Lana | 12:58 |
Re: select query does not pick up the right index | David Rowley | 13:01 |
RE: select query does not pick up the right index | Abadie Lana | 13:13 |
Re: select query does not pick up the right index | David Rowley | 13:17 |
RE: select query does not pick up the right index | Abadie Lana | 13:20 |
RE: select query does not pick up the right index | Abadie Lana | 14:34 |
Re: select query does not pick up the right index | David Rowley | 21:42 |
Re: select query does not pick up the right index | Justin Pryzby | 23:47 |
Thread | Author | Time |
---|---|---|
RE: select query does not pick up the right index | Abadie Lana | 08:10 |
RE: select query does not pick up the right index | Abadie Lana | 08:17 |
RE: select query does not pick up the right index | Abadie Lana | 08:58 |
Thread | Author | Time |
---|---|---|
Re: select query does not pick up the right index | Justin Pryzby | 04:23 |
Thread | Author | Time |
---|---|---|
RE: select query does not pick up the right index | Abadie Lana | 16:09 |
Thread | Author | Time |
---|---|---|
Re: select query does not pick up the right index | Justin Pryzby | 08:15 |
Thread | Author | Time |
---|---|---|
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Etsuro Fujita | 02:21 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 📎 | Amit Langote | 04:46 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Amit Langote | 04:49 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Etsuro Fujita | 11:04 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Etsuro Fujita | 11:10 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 📎 | Etsuro Fujita | 12:50 |
Thread | Author | Time |
---|---|---|
Re: Detect missing combined indexes (automatically) | Jim Finnerty | 15:47 |
Thread | Author | Time |
---|---|---|
Re: Detect missing combined indexes (automatically) | Thomas Kellerer | 07:19 |
Re: Detect missing combined indexes (automatically) | Julien Rouhaud | 07:42 |
Thread | Author | Time |
---|---|---|
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Amit Langote | 01:46 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Amit Langote | 01:51 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Amit Langote | 02:42 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Ashutosh Bapat | 04:29 |
Re: Detect missing combined indexes (automatically) | Thomas Güttler | 09:23 |
Re: Detect missing combined indexes (automatically) | Julien Rouhaud | 10:25 |
Thread | Author | Time |
---|---|---|
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Etsuro Fujita | 05:41 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Etsuro Fujita | 05:45 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Etsuro Fujita | 05:52 |
No matching tables have ever been vacuumed | Daulat Ram | 07:06 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Etsuro Fujita | 11:21 |
Parallel stats in execution plans | David Conlin | 11:31 |
Thread | Author | Time |
---|---|---|
Re: No matching tables have ever been vacuumed | Laurenz Albe | 09:49 |
autovacuum doesnt run on the pg_toast_id table | Mariel Cherkassky | 17:28 |
Re: autovacuum doesnt run on the pg_toast_id table | Justin Pryzby | 17:46 |
Re: autovacuum doesnt run on the pg_toast_id table | Alvaro Herrera | 17:52 |
Re: autovacuum doesnt run on the pg_toast_id table | Mariel Cherkassky | 17:58 |
Re: autovacuum doesnt run on the pg_toast_id table | Alvaro Herrera | 19:09 |
Re: autovacuum doesnt run on the pg_toast_id table | Mariel Cherkassky | 19:59 |
Re: autovacuum doesnt run on the pg_toast_id table | Alvaro Herrera | 20:16 |
Re: autovacuum doesnt run on the pg_toast_id table | Mariel Cherkassky | 20:18 |
Thread | Author | Time |
---|---|---|
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 📎 | Etsuro Fujita | 12:55 |
JIT overhead slowdown 📎 | Luis Carril | 14:12 |
Re: JIT overhead slowdown | Andres Freund | 16:42 |
Re: JIT overhead slowdown | Luis Carril | 18:02 |
Thread | Author | Time |
---|---|---|
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Amit Langote | 12:17 |
Thread | Author | Time |
---|---|---|
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Etsuro Fujita | 08:17 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Amit Langote | 08:21 |
Re: Query with high planning time at version 11.1 compared versions 10.5 and 11.0 | Etsuro Fujita | 08:56 |
Memory and hard ware calculation : | Rangaraj G | 11:24 |
Re: Memory and hard ware calculation : | Cleiton Luiz Domazak | 17:43 |
Thread | Author | Time |
---|---|---|
Re: Memory and hard ware calculation : | Fabio Pardi | 08:11 |
RE: Memory and hard ware calculation : | Rangaraj G | 12:54 |
Very long query planning times for database with lots of partitions | Mickael van der Beek | 13:44 |
Re: Very long query planning times for database with lots of partitions | Justin Pryzby | 14:02 |
RE: Very long query planning times for database with lots of partitions | Steven Winfield | 14:07 |
Re: Very long query planning times for database with lots of partitions | Mickael van der Beek | 15:24 |
Re: [HACKERS] proposal: schema variables 📎 | Pavel Stehule | 19:32 |
SELECT performance drop | Jan Nielsen | 20:04 |
Re: Memory and hard ware calculation : | Ron | 20:05 |
Re: SELECT performance drop | Jan Nielsen | 21:00 |
ANALYZE accuracy problems for n_distinct, and a solution | Jim Finnerty | 21:13 |
Re: SELECT performance drop | legrand legrand | 21:55 |
Re: SELECT performance drop | Jan Nielsen | 22:28 |
Thread | Author | Time |
---|---|---|
Re: SELECT performance drop | Jim Finnerty | 13:50 |
ERROR: found xmin from before relfrozenxid | Mariel Cherkassky | 15:25 |
Re: SELECT performance drop | Jan Nielsen | 17:28 |
Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? | Saurabh Nanda | 19:16 |
RE:SELECT performance drop | legrand legrand | 19:37 |
Re: ERROR: found xmin from before relfrozenxid | Jerry Sievers | 19:42 |
Re: SELECT performance drop | Laurenz Albe | 22:41 |
Thread | Author | Time |
---|---|---|
Re: ERROR: found xmin from before relfrozenxid | Mariel Cherkassky | 06:32 |
Re: Parallel stats in execution plans | David Conlin | 08:18 |
Re: Parallel stats in execution plans | David Rowley | 11:55 |
Re: ERROR: found xmin from before relfrozenxid | Mariel Cherkassky | 14:14 |
RE: dsa_allocate() faliure 📎 | Arne Roland | 14:44 |
Re: SELECT performance drop | Jan Nielsen | 16:52 |
Re: SELECT performance drop | Jan Nielsen | 18:04 |
Thread | Author | Time |
---|---|---|
Re: ERROR: found xmin from before relfrozenxid | Adrien NAYRAT | 10:48 |
Re: ERROR: found xmin from before relfrozenxid | Mariel Cherkassky | 10:56 |
Re: ERROR: found xmin from before relfrozenxid | Adrien NAYRAT | 10:59 |
Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? | Saurabh Nanda | 11:10 |
Thread | Author | Time |
---|---|---|
Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? | Saurabh Nanda | 07:39 |
Q on SQL Performance tuning | Bhupathi, Kaushik (CORP) | 08:43 |
Re: Q on SQL Performance tuning | legrand legrand | 11:28 |
Re: Q on SQL Performance tuning | Justin Pryzby | 14:31 |
Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? | Justin Pryzby | 16:04 |
Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? | Saurabh Nanda | 16:38 |
Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? | Jeff Janes | 17:48 |
Re: Benchmarking: How to identify bottleneck (limiting factor) and achieve "linear scalability"? | Jeff Janes | 19:41 |
Thread | Author | Time |
---|---|---|
Re: dsa_allocate() faliure | Thomas Munro | 03:13 |
Re: Will higher shared_buffers improve tpcb-like benchmarks? | Saurabh Nanda | 03:50 |
Re: ERROR: found xmin from before relfrozenxid | Mariel Cherkassky | 07:51 |
Re: ERROR: found xmin from before relfrozenxid | Alvaro Herrera | 09:13 |
Re: dsa_allocate() faliure | Fabio Isabettini | 09:53 |
Re: ERROR: found xmin from before relfrozenxid | Mariel Cherkassky | 10:35 |
pgstattupple vs pg_total_relation_size | Mariel Cherkassky | 10:41 |
Re: How can sort performance be so different | Bob Jolliffe | 11:57 |
Re: pgstattupple vs pg_total_relation_size | Tumasgiu Rossini | 13:19 |
Re: pgstattupple vs pg_total_relation_size | Jehan-Guillaume (ioguix) de Rorthais | 13:27 |
Re: pgstattupple vs pg_total_relation_size | Mariel Cherkassky | 14:32 |
Re: pgstattupple vs pg_total_relation_size | Tom Lane | 14:46 |
Re: [HACKERS] proposal: schema variables 📎 | Pavel Stehule | 16:34 |
Re: How can sort performance be so different | Peter Geoghegan | 23:54 |
Thread | Author | Time |
---|---|---|
Setting effective_cache size | Nandakumar M | 07:30 |
Re: Setting effective_cache size | Nandakumar M | 07:34 |
Re: [HACKERS] proposal: schema variables 📎 | Pavel Stehule | 11:49 |
Re: Setting effective_cache size | Laurenz Albe | 11:57 |
Re: How can sort performance be so different | Bob Jolliffe | 13:29 |