pgsql-performance  

Messages by Thread

• • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
  • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
  • Re: Big performance slowdown from 11.2 to 13.3 Justin Pryzby
  • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
  • Re: Big performance slowdown from 11.2 to 13.3 Justin Pryzby
  • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
  • Re: Big performance slowdown from 11.2 to 13.3 Justin Pryzby
  • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
  • Re: Big performance slowdown from 11.2 to 13.3 Peter Geoghegan
  • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
  • Re: Big performance slowdown from 11.2 to 13.3 Alvaro Herrera
  • Re: Big performance slowdown from 11.2 to 13.3 Peter Geoghegan
  • Re: Big performance slowdown from 11.2 to 13.3 David Rowley
  • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
  • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
  • Re: Big performance slowdown from 11.2 to 13.3 Vijaykumar Jain
  • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
  • Re: Big performance slowdown from 11.2 to 13.3 Vijaykumar Jain
  • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
  • Re: Big performance slowdown from 11.2 to 13.3 Michael Lewis
  • RE: Big performance slowdown from 11.2 to 13.3 l...@laurent-hasson.com
• Re: Linear slow-down while inserting into a table with an ON INSERT trigger ? Justin Pryzby
  • Re: Linear slow-down while inserting into a table with an ON INSERT trigger ? David Rowley
  • Re: Linear slow-down while inserting into a table with an ON INSERT trigger ? Tom Lane
  • Re: Linear slow-down while inserting into a table with an ON INSERT trigger ? Tobias Gierke
  • Re: Linear slow-down while inserting into a table with an ON INSERT trigger ? Tobias Gierke
  • Re: Linear slow-down while inserting into a table with an ON INSERT trigger ? Laurenz Albe
• temporary file log lines MichaelDBA
  • Re: temporary file log lines Laurenz Albe
  • Re: temporary file log lines MichaelDBA
  • Re: temporary file log lines Guillaume Lelarge
  • Re: temporary file log lines Tomas Vondra
• ERROR: there is no unique or exclusion constraint matching the ON CONFLICT specification Nagaraj Raj
• Strange execution plan Joel Frid
  • Strange execution plan Joel Frid
  • Re: Strange execution plan Manuel Weitzman
  • Re: Strange execution plan Manuel Weitzman
  • Re: Strange execution plan Manuel Weitzman
• ETL - sql orchestrator is stuck when there is not sleep() between queries Allan Barrielle
  • Re: ETL - sql orchestrator is stuck when there is not sleep() between queries Justin Pryzby
  • Re: ETL - sql orchestrator is stuck when there is not sleep() between queries Allan Barrielle
  • Re: ETL - sql orchestrator is stuck when there is not sleep() between queries Justin Pryzby
  • Re: ETL - sql orchestrator is stuck when there is not sleep() between queries Allan Barrielle
  • Re: ETL - sql orchestrator is stuck when there is not sleep() between queries Allan Barrielle
  • Re: ETL - sql orchestrator is stuck when there is not sleep() between queries Imre Samu
• slow performance with cursor Ayub Khan
  • Re: slow performance with cursor Justin Pryzby
  • Re: slow performance with cursor Ayub Khan
  • Re: slow performance with cursor Tom Lane
  • Re: slow performance with cursor Ayub Khan
  • Re: slow performance with cursor Justin Pryzby
  • Re: slow performance with cursor Ayub Khan
  • Re: slow performance with cursor Tomas Vondra
• Partition column should be part of PK Nagaraj Raj
  • Re: Partition column should be part of PK Justin Pryzby
  • Re: Partition column should be part of PK Justin Pryzby
  • Re: Partition column should be part of PK Alvaro Herrera
  • RE: Partition column should be part of PK Mike Sofen
  • Re: Partition column should be part of PK Nagaraj Raj
  • Re: Partition column should be part of PK Christophe Pettus
  • Re: Partition column should be part of PK Nagaraj Raj
  • Re: Partition column should be part of PK Christophe Pettus
  • Re: Partition column should be part of PK David Rowley
  • Re: Partition column should be part of PK Thomas Kellerer
  • RE: Partition column should be part of PK Michel SALAIS
  • Re: Partition column should be part of PK Justin Pryzby
  • Performance benchmark of PG Manish Lad
  • Re: Performance benchmark of PG Laurenz Albe
  • Re: Performance benchmark of PG Manish Lad
  • Re: Performance benchmark of PG Hüseyin Demir
  • Re: Performance benchmark of PG Thomas Kellerer
  • Re: Performance benchmark of PG Manish Lad
  • Re: Performance benchmark of PG Ninad Shah
  • Re: Performance benchmark of PG Manish Lad
• Estimating wal_keep_size Dean Gibson (DB Administrator)
  • Re: Estimating wal_keep_size Julien Rouhaud
  • Re: Estimating wal_keep_size Dean Gibson (DB Administrator)
  • Re: Estimating wal_keep_size Julien Rouhaud
  • Re: Estimating wal_keep_size Vijaykumar Jain
  • Re: Estimating wal_keep_size Dean Gibson (DB Administrator)
• PostgreSQL V13 Replication Issue Haseeb Khan
  • Re: PostgreSQL V13 Replication Issue Dean Gibson (DB Administrator)
  • Re: PostgreSQL V13 Replication Issue Michael Paquier
• Master - Slave Replication Window Server Haseeb Khan
  • Re: Master - Slave Replication Window Server Rory Campbell-Lange
  • Re: Master - Slave Replication Window Server Haseeb Khan
  • Re: Master - Slave Replication Window Server Haseeb Khan
  • Re: Master - Slave Replication Window Server Rory Campbell-Lange
  • Re: Master - Slave Replication Window Server Haseeb Khan
  • Re: Master - Slave Replication Window Server Atul Kumar
• overcommit_ratio setting Yi Sun
  • Re: overcommit_ratio setting Julien Rouhaud
  • Re: overcommit_ratio setting Laurenz Albe
  • Re: overcommit_ratio setting Yi Sun
  • Re: overcommit_ratio setting Laurenz Albe
  • Re: overcommit_ratio setting Yi Sun
• Page File Size Reached Critical Threshold PostgreSQL V13 Haseeb Khan
  • Re: Page File Size Reached Critical Threshold PostgreSQL V13 Justin Pryzby
  • Re: Page File Size Reached Critical Threshold PostgreSQL V13 Haseeb Khan
  • Re: Page File Size Reached Critical Threshold PostgreSQL V13 Justin Pryzby
  • Re: Page File Size Reached Critical Threshold PostgreSQL V13 Justin Pryzby
• Re: waiting for client write Magnus Hagander
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Jeff Janes
  • Re: waiting for client write Vijaykumar Jain
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Pavan Pusuluri
  • Re: waiting for client write Ranier Vilela
  • Re: waiting for client write Jeff Janes
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Ranier Vilela
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Ranier Vilela
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Ranier Vilela
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Ranier Vilela
  • Re: waiting for client write Vijaykumar Jain
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Vijaykumar Jain
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Ayub Khan
  • Re: waiting for client write Vijaykumar Jain
• dexter on AWS RDS auto tune queries Ayub Khan
  • Re: dexter on AWS RDS auto tune queries Julien Rouhaud
  • Re: dexter on AWS RDS auto tune queries Christophe Pettus
  • Re: dexter on AWS RDS auto tune queries Ayub Khan
  • Re: dexter on AWS RDS auto tune queries Julien Rouhaud
  • Re: dexter on AWS RDS auto tune queries Ayub Khan
• query planner not using index, instead using squential scan Ayub Khan
  • Re: query planner not using index, instead using squential scan Tom Lane
  • Re: query planner not using index, instead using squential scan Vijaykumar Jain
  • Re: query planner not using index, instead using squential scan Ayub Khan
  • Re: query planner not using index, instead using squential scan Vijaykumar Jain
• PgSQL 12 on WinSrv ~3x faster than on Linux Taras Savchuk
  • Re: PgSQL 12 on WinSrv ~3x faster than on Linux David Rowley
  • Re: PgSQL 12 on WinSrv ~3x faster than on Linux Vijaykumar Jain
  • Re: PgSQL 12 on WinSrv ~3x faster than on Linux Tom Lane
  • RE: PgSQL 12 on WinSrv ~3x faster than on Linux Taras Savchuk
• slow query with inline function on AWS RDS with RDS 24x large Ayub Khan
  • Re: slow query with inline function on AWS RDS with RDS 24x large Pavel Stehule
  • Re: slow query with inline function on AWS RDS with RDS 24x large Ayub Khan
  • Re: slow query with inline function on AWS RDS with RDS 24x large Pavel Stehule
  • Re: slow query with inline function on AWS RDS with RDS 24x large Ayub Khan
• Re: AWS forcing PG upgrade from v9.6 a disaster Andrew Dunstan
  • Re: AWS forcing PG upgrade from v9.6 a disaster Campbell, Lance
  • Re: AWS forcing PG upgrade from v9.6 a disaster MichaelDBA
  • Re: AWS forcing PG upgrade from v9.6 a disaster Ryan Bair
  • Re: AWS forcing PG upgrade from v9.6 a disaster Michael Lewis
  • Re: AWS forcing PG upgrade from v9.6 a disaster Pavel Stehule
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Jan Wieck
  • Re: AWS forcing PG upgrade from v9.6 a disaster Andrew Dunstan
  • Re: AWS forcing PG upgrade from v9.6 a disaster Bruce Momjian
  • Re: AWS forcing PG upgrade from v9.6 a disaster Christophe Pettus
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Alexey M Boltenkov
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Bob Lunney
  • Re: AWS forcing PG upgrade from v9.6 a disaster Jan Wieck
  • Re: AWS forcing PG upgrade from v9.6 a disaster Andrew Dunstan
  • Re: AWS forcing PG upgrade from v9.6 a disaster Jan Wieck
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Andrew Dunstan
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Andrew Dunstan
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Christophe Pettus
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Tom Lane
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Justin Pryzby
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Andrew Dunstan
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Ranier Vilela
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Tom Lane
  • Re: AWS forcing PG upgrade from v9.6 a disaster Andrew Dunstan
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • pg_dumpall --exclude-database case folding, was Re: AWS forcing PG upgrade from v9.6 a disaster Andrew Dunstan
  • Re: pg_dumpall --exclude-database case folding, was Re: AWS forcing PG upgrade from v9.6 a disaster Tom Lane
  • Re: AWS forcing PG upgrade from v9.6 a disaster Dean Gibson (DB Administrator)
  • Re: AWS forcing PG upgrade from v9.6 a disaster Joshua Drake
• Count (select 1) subquery as constant Eugen Konkov
• issue partition scan Nagaraj Raj
  • Re: issue partition scan Christophe Pettus
  • Re: issue partition scan Nagaraj Raj

• Earlier messages
• Later messages