pgsql-performance  

Messages by Thread

• 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
  • Re: issue partition scan David Rowley
  • Re: issue partition scan Christophe Pettus
• Optimising outer joins in the presence of non-nullable references Philip Lykke Carlsen
  • Re: Optimising outer joins in the presence of non-nullable references Tom Lane
• transaction blocking on COMMIT Bob Jolliffe
  • Re: transaction blocking on COMMIT Vijaykumar Jain
  • Re: transaction blocking on COMMIT Bob Jolliffe
  • Re: transaction blocking on COMMIT Vijaykumar Jain
  • Re: transaction blocking on COMMIT Bob Jolliffe
  • Re: transaction blocking on COMMIT Christophe Pettus
  • Re: transaction blocking on COMMIT Alexey M Boltenkov
  • Re: transaction blocking on COMMIT Bob Jolliffe
• logical replication Marc Millas
  • Re: logical replication Andrew Dunstan
  • Re: logical replication Marc Millas
• Partition with check constraint with "like" Nagaraj Raj
  • Re: Partition with check constraint with "like" David Rowley
  • Re: Partition with check constraint with "like" Nagaraj Raj
  • Re: Partition with check constraint with "like" Justin Pryzby
  • Re: Partition with check constraint with "like" Michael Lewis
  • Re: Partition with check constraint with "like" Nagaraj Raj
  • Re: Partition with check constraint with "like" David Rowley
  • Re: Partition with check constraint with "like" Nagaraj Raj
  • Re: Partition with check constraint with "like" Vijaykumar Jain
  • Re: Partition with check constraint with "like" Nagaraj Raj
  • RE: Partition with check constraint with "like" Michel SALAIS
  • Re: Partition with check constraint with "like" Nagaraj Raj
  • Re: Partition with check constraint with "like" Nagaraj Raj
  • RE: Partition with check constraint with "like" Michel SALAIS
  • Re: Partition with check constraint with "like" David Rowley
  • Re: Partition with check constraint with "like" David Rowley
• Index and statistics not used rstander
  • Re: Index and statistics not used David Rowley
• Very slow "bloat query" Marcin Gozdalik
  • Re: Very slow "bloat query" Gilles Darold
  • Re: Very slow "bloat query" Imre Samu
  • Re: Very slow "bloat query" Marcin Gozdalik
  • Re: Very slow "bloat query" Imre Samu
  • Re: Very slow "bloat query" Marcin Gozdalik
  • Re: Very slow "bloat query" Tom Lane
  • Re: Very slow "bloat query" Marcin Gozdalik
• Re: BUG #16968: Planner does not recognize optimization David Rowley
  • Re: BUG #16968: Planner does not recognize optimization KES
  • Re: BUG #16968: Planner does not recognize optimization David Rowley
  • Re: BUG #16968: Planner does not recognize optimization Eugen Konkov
  • Re: BUG #16968: Planner does not recognize optimization David Rowley
  • Re: BUG #16968: Planner does not recognize optimization Eugen Konkov
• PostgreSQL blocked locks query Manoj Kumar
  • Re: PostgreSQL blocked locks query Justin Pryzby
  • RE: Re: PostgreSQL blocked locks query Manoj Kumar
• Very slow Query compared to Oracle / SQL - Server Semen Yefimenko
  • Re: Very slow Query compared to Oracle / SQL - Server luis . roberto
  • Re: Very slow Query compared to Oracle / SQL - Server Alexey M Boltenkov
  • Re: Very slow Query compared to Oracle / SQL - Server Alexey M Boltenkov
  • Re: Very slow Query compared to Oracle / SQL - Server Semen Yefimenko
  • Re: Very slow Query compared to Oracle / SQL - Server Andreas Joseph Krogh
  • Re: Very slow Query compared to Oracle / SQL - Server Vijaykumar Jain
  • Re: Very slow Query compared to Oracle / SQL - Server Alexey M Boltenkov
  • Re: Very slow Query compared to Oracle / SQL - Server Alexey M Boltenkov
  • Re: Very slow Query compared to Oracle / SQL - Server Alexey M Boltenkov
  • Re: Very slow Query compared to Oracle / SQL - Server Justin Pryzby
  • Re: Very slow Query compared to Oracle / SQL - Server Imre Samu
  • Re: Very slow Query compared to Oracle / SQL - Server Semen Yefimenko
  • Re: Very slow Query compared to Oracle / SQL - Server Vijaykumar Jain
  • Re: Very slow Query compared to Oracle / SQL - Server Semen Yefimenko
  • Re: Very slow Query compared to Oracle / SQL - Server Vijaykumar Jain
  • Re: Very slow Query compared to Oracle / SQL - Server Semen Yefimenko
  • Re: Very slow Query compared to Oracle / SQL - Server Justin Pryzby
  • Re: Very slow Query compared to Oracle / SQL - Server Tom Lane
  • Re: Very slow Query compared to Oracle / SQL - Server Peter Geoghegan
  • Re: Very slow Query compared to Oracle / SQL - Server Peter Geoghegan
  • Re: Very slow Query compared to Oracle / SQL - Server didier
  • Re: Very slow Query compared to Oracle / SQL - Server Semen Yefimenko
  • Re: Very slow Query compared to Oracle / SQL - Server Semen Yefimenko
  • Re: Very slow Query compared to Oracle / SQL - Server Rick Otten
• 15x slower PreparedStatement vs raw query Alex

• Earlier messages
• Later messages