pgsql-performance  

Messages by Thread

• • Re: Postgres using the wrong index index Justin Pryzby
  • Re: Postgres using the wrong index index Matt Dupree
  • Re: Postgres using the wrong index index Justin Pryzby
• Slow query because lexeme index not used Alex
  • Re: Slow query because lexeme index not used Justin Pryzby
  • Re: Slow query because lexeme index not used Alex
• Logical Replication speed-up initial data Nikhil Shetty
  • Re: Logical Replication speed-up initial data Hüseyin Demir
  • Re: Logical Replication speed-up initial data Stefano Amoroso
  • Re: Logical Replication speed-up initial data Nikhil Shetty
  • Re: Logical Replication speed-up initial data Nikhil Shetty
  • Re: Logical Replication speed-up initial data Rick Otten
  • Re: Logical Replication speed-up initial data Vijaykumar Jain
  • Re: Logical Replication speed-up initial data Avinash Kumar
  • Re: Logical Replication speed-up initial data Nikhil Shetty
  • Re: Logical Replication speed-up initial data Nikhil Shetty
  • Re: Logical Replication speed-up initial data Vijaykumar Jain
  • Re: Logical Replication speed-up initial data Jeff Janes
  • Re: Logical Replication speed-up initial data Christophe Pettus
• Performance issue with thousands of calls to procedures and functions? Daniel Westermann (DWE)
  • Re: Performance issue with thousands of calls to procedures and functions? Imre Samu
  • Re: Performance issue with thousands of calls to procedures and functions? Pavel Stehule
  • Re: Performance issue with thousands of calls to procedures and functions? Pavel Stehule
  • Re: Performance issue with thousands of calls to procedures and functions? Pavel Stehule
  • Re: Performance issue with thousands of calls to procedures and functions? Daniel Westermann (DWE)
  • Re: Performance issue with thousands of calls to procedures and functions? Pavel Stehule
  • Re: Performance issue with thousands of calls to procedures and functions? Daniel Westermann (DWE)
• Query performance ! kenny a
  • Query performance ! kenny a
  • Re: Query performance ! Bruce Momjian
  • Re: Query performance ! Justin Pryzby
• Performance of lateral join Simen Andreas Andreassen Lønsethagen
  • Re: Performance of lateral join Justin Pryzby
  • Re: Performance of lateral join Simen Andreas Andreassen Lønsethagen
  • Re: Performance of lateral join Justin Pryzby
• Performance Issue on a table Manoj Kumar
  • Re: Performance Issue on a table Justin Pryzby
• Partitioned table statistics vs autoanalyze Kamil Frydel
  • Re: Partitioned table statistics vs autoanalyze Justin Pryzby
  • Re: Partitioned table statistics vs autoanalyze Kamil Frydel
• Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Justin Pryzby
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Peter Geoghegan
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 David Rowley
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • Re: Big performance slowdown from 11.2 to 13.3 David Rowley
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • Re: Big performance slowdown from 11.2 to 13.3 Peter Geoghegan
  • Re: Big performance slowdown from 11.2 to 13.3 Justin Pryzby
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • Re: Big performance slowdown from 11.2 to 13.3 Peter Geoghegan
  • Re: Big performance slowdown from 11.2 to 13.3 Peter Geoghegan
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • Re: Big performance slowdown from 11.2 to 13.3 Peter Geoghegan
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • Re: Big performance slowdown from 11.2 to 13.3 Peter Geoghegan
  • Re: Big performance slowdown from 11.2 to 13.3 Ranier Vilela
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 David G. Johnston
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Justin Pryzby
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Justin Pryzby
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Justin Pryzby
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Peter Geoghegan
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • 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 [email protected]
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Tom Lane
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Vijaykumar Jain
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Vijaykumar Jain
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
  • Re: Big performance slowdown from 11.2 to 13.3 Michael Lewis
  • RE: Big performance slowdown from 11.2 to 13.3 [email protected]
• 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

• Earlier messages
• Later messages