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 |
---|---|---|
Re: AWS forcing PG upgrade from v9.6 a disaster | Justin Pryzby | 04:16 |
Re: AWS forcing PG upgrade from v9.6 a disaster | Dean Gibson (DB Administrator) | 17:44 |
Thread | Author | Time |
---|---|---|
slow query with inline function on AWS RDS with RDS 24x large | Ayub Khan | 08:06 |
Re: slow query with inline function on AWS RDS with RDS 24x large | Pavel Stehule | 08:22 |
Re: slow query with inline function on AWS RDS with RDS 24x large | Ayub Khan | 08:32 |
Re: slow query with inline function on AWS RDS with RDS 24x large | Pavel Stehule | 08:40 |
Re: slow query with inline function on AWS RDS with RDS 24x large | Ayub Khan | 08:51 |
PgSQL 12 on WinSrv ~3x faster than on Linux | Taras Savchuk | 11:53 |
Re: PgSQL 12 on WinSrv ~3x faster than on Linux | David Rowley | 12:42 |
Re: PgSQL 12 on WinSrv ~3x faster than on Linux | Vijaykumar Jain | 13:14 |
Re: PgSQL 12 on WinSrv ~3x faster than on Linux | Tom Lane | 13:40 |
RE: PgSQL 12 on WinSrv ~3x faster than on Linux | Taras Savchuk | 14:01 |
Thread | Author | Time |
---|---|---|
query planner not using index, instead using squential scan | Ayub Khan | 16:42 |
Re: query planner not using index, instead using squential scan | Tom Lane | 19:29 |
Re: query planner not using index, instead using squential scan | Vijaykumar Jain | 19:52 |
Re: query planner not using index, instead using squential scan | Ayub Khan | 21:14 |
Re: query planner not using index, instead using squential scan | Vijaykumar Jain | 21:18 |
Thread | Author | Time |
---|---|---|
Re: AWS forcing PG upgrade from v9.6 a disaster | Dean Gibson (DB Administrator) | 23:49 |
Thread | Author | Time |
---|---|---|
dexter on AWS RDS auto tune queries | Ayub Khan | 04:51 |
Re: dexter on AWS RDS auto tune queries | Julien Rouhaud | 04:57 |
Re: dexter on AWS RDS auto tune queries | Christophe Pettus | 05:00 |
Re: dexter on AWS RDS auto tune queries | Ayub Khan | 07:49 |
Re: dexter on AWS RDS auto tune queries | Julien Rouhaud | 07:57 |
Re: dexter on AWS RDS auto tune queries | Ayub Khan | 10:05 |
Re: AWS forcing PG upgrade from v9.6 a disaster | Andrew Dunstan | 11:52 |
Re: AWS forcing PG upgrade from v9.6 a disaster | Dean Gibson (DB Administrator) | 17:27 |
Thread | Author | Time |
---|---|---|
slow query | Ayub Khan | 16:03 |
Re: slow query | Christophe Pettus | 16:08 |
Re: slow query | Ayub Khan | 16:32 |
Re: slow query | Tom Lane | 17:14 |
Re: slow query | Ayub Khan | 17:43 |
Thread | Author | Time |
---|---|---|
waiting for client write 📎 | Ayub Khan | 14:47 |
Re: waiting for client write | Magnus Hagander | 14:49 |
Re: waiting for client write | Ayub Khan | 18:59 |
Re: slow query | Jeff Janes | 19:57 |
Re: slow query | Ayub Khan | 20:23 |
Thread | Author | Time |
---|---|---|
Re: waiting for client write | Ayub Khan | 16:28 |
Re: waiting for client write | Pavan Pusuluri | 16:46 |
Re: waiting for client write | Ranier Vilela | 16:52 |
Re: waiting for client write | Ayub Khan | 16:59 |
Re: waiting for client write | Ranier Vilela | 17:37 |
Re: waiting for client write | Ayub Khan | 17:59 |
Re: waiting for client write | Ranier Vilela | 18:03 |
Re: waiting for client write | Ayub Khan | 18:19 |
Re: waiting for client write | Ranier Vilela | 18:25 |
Re: waiting for client write | Ayub Khan | 19:45 |
Re: waiting for client write | Jeff Janes | 21:58 |
Re: waiting for client write | Ayub Khan | 22:06 |
Thread | Author | Time |
---|---|---|
Re: waiting for client write | Ayub Khan | 08:19 |
Re: waiting for client write | Ranier Vilela | 12:03 |
Re: waiting for client write | Vijaykumar Jain | 12:04 |
Re: waiting for client write | Ayub Khan | 12:34 |
Thread | Author | Time |
---|---|---|
Re: waiting for client write | Ayub Khan | 14:00 |
Re: waiting for client write | Vijaykumar Jain | 16:30 |
Re: waiting for client write | Ayub Khan | 17:00 |
Thread | Author | Time |
---|---|---|
Re: waiting for client write | Ayub Khan | 05:02 |
overcommit_ratio setting | Yi Sun | 10:16 |
pg_dumpall --exclude-database case folding, was Re: AWS forcing PG upgrade from v9.6 a disaster | Andrew Dunstan | 13:21 |
Re: pg_dumpall --exclude-database case folding, was Re: AWS forcing PG upgrade from v9.6 a disaster | Tom Lane | 13:32 |
pg_dumpall --exclude-database case folding | Andrew Dunstan | 13:46 |
Re: overcommit_ratio setting | Julien Rouhaud | 14:14 |
Re: overcommit_ratio setting | Laurenz Albe | 16:18 |
Re: Planning performance problem (67626.278ms) | Manuel Weitzman | 17:25 |
Master - Slave Replication Window Server | Haseeb Khan | 19:36 |
Re: Master - Slave Replication Window Server | Rory Campbell-Lange | 19:41 |
Thread | Author | Time |
---|---|---|
Re: overcommit_ratio setting | Yi Sun | 00:34 |
Re: Master - Slave Replication Window Server | Haseeb Khan | 05:42 |
Re: Master - Slave Replication Window Server | Haseeb Khan | 06:17 |
Re: overcommit_ratio setting | Laurenz Albe | 07:07 |
Re: overcommit_ratio setting | Yi Sun | 07:45 |
Re: Master - Slave Replication Window Server | Rory Campbell-Lange | 12:05 |
Re: Master - Slave Replication Window Server | Haseeb Khan | 12:29 |
Re: waiting for client write | Ayub Khan | 15:43 |
Re: Master - Slave Replication Window Server 📎 | Atul Kumar | 16:14 |
Re: waiting for client write | Vijaykumar Jain | 17:22 |
Thread | Author | Time |
---|---|---|
PostgreSQL V13 Replication Issue | Haseeb Khan | 16:25 |
Re: PostgreSQL V13 Replication Issue | Dean Gibson (DB Administrator) | 16:30 |
Thread | Author | Time |
---|---|---|
Estimating wal_keep_size | Dean Gibson (DB Administrator) | 00:36 |
Re: Estimating wal_keep_size | Julien Rouhaud | 01:02 |
Re: PostgreSQL V13 Replication Issue | Michael Paquier | 01:02 |
Thread | Author | Time |
---|---|---|
Re: Estimating wal_keep_size | Dean Gibson (DB Administrator) | 18:13 |
Re: Estimating wal_keep_size | Julien Rouhaud | 18:27 |
Re: Estimating wal_keep_size | Vijaykumar Jain | 18:40 |
Thread | Author | Time |
---|---|---|
Re: Planning performance problem (67626.278ms) 📎 | Manuel Weitzman | 00:09 |
Re: Planning performance problem (67626.278ms) | Tom Lane | 21:06 |
Re: Planning performance problem (67626.278ms) | Ranier Vilela | 23:23 |
Re: Estimating wal_keep_size | Dean Gibson (DB Administrator) | 23:53 |
Thread | Author | Time |
---|---|---|
Re: Planning performance problem (67626.278ms) | Tom Lane | 00:17 |
Thread | Author | Time |
---|---|---|
Partition column should be part of PK | Nagaraj Raj | 03:10 |
Re: Partition column should be part of PK | Justin Pryzby | 04:22 |
slow performance with cursor | Ayub Khan | 16:09 |
Re: slow performance with cursor | Justin Pryzby | 16:21 |
Re: slow performance with cursor | Ayub Khan | 16:37 |
Re: slow performance with cursor | Tom Lane | 18:04 |
Thread | Author | Time |
---|---|---|
Re: Planning performance problem (67626.278ms) | Manuel Weitzman | 19:26 |
Re: Planning performance problem (67626.278ms) | Tom Lane | 19:43 |
Re: Planning performance problem (67626.278ms) 📎 | Manuel Weitzman | 21:35 |
Re: Planning performance problem (67626.278ms) | Tom Lane | 22:31 |
Thread | Author | Time |
---|---|---|
Re: Planning performance problem (67626.278ms) | Manuel Weitzman | 20:56 |