pgsql-performance  

Messages by Thread

• • 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
  • Re: 15x slower PreparedStatement vs raw query Justin Pryzby
  • Re: 15x slower PreparedStatement vs raw query Alex
  • Re: 15x slower PreparedStatement vs raw query Rick Otten
  • Re: 15x slower PreparedStatement vs raw query Alex
  • Re: 15x slower PreparedStatement vs raw query Laurenz Albe
  • Re: 15x slower PreparedStatement vs raw query Vijaykumar Jain
  • Re: 15x slower PreparedStatement vs raw query David Rowley
  • Re: 15x slower PreparedStatement vs raw query Alex
  • Re: 15x slower PreparedStatement vs raw query Justin Pryzby
• Log number of tuples returned Edson Richter
  • Re: Log number of tuples returned Justin Pryzby
  • RES: Log number of tuples returned Edson Richter
• Error while calling proc with table type from Application aditya desai
  • Re: Error while calling proc with table type from Application (npgsql) Justin Pryzby
  • Re: Error while calling proc with table type from Application (npgsql) aditya desai
  • Re: Error while calling proc with table type from Application (npgsql) aditya desai
  • Re: Error while calling proc with table type from Application (npgsql) Vijaykumar Jain
• Order of execution luis . roberto
  • Re: Order of execution Jean-Christophe Boggio
• Does btrfs on Linux have a negative performance impact for PostgreSQL 13? Simon Connah
  • Re: Does btrfs on Linux have a negative performance impact for PostgreSQL 13? Justin Pryzby
  • Re: Does btrfs on Linux have a negative performance impact for PostgreSQL 13? Bruce Momjian
  • Re: Does btrfs on Linux have a negative performance impact for PostgreSQL 13? Marc Millas
  • Re: Does btrfs on Linux have a negative performance impact for PostgreSQL 13? Rory Campbell-Lange
  • Re: Does btrfs on Linux have a negative performance impact for PostgreSQL 13? Marc Millas
  • Re: Does btrfs on Linux have a negative performance impact for PostgreSQL 13? Christophe Pettus
  • Re: Does btrfs on Linux have a negative performance impact for PostgreSQL 13? Tomas Vondra
  • Re: Does btrfs on Linux have a negative performance impact for PostgreSQL 13? Rory Campbell-Lange
  • Re: Does btrfs on Linux have a negative performance impact for PostgreSQL 13? Simon Connah
• hint in determining effective_io_concurrency Luca Ferrari
  • Re: hint in determining effective_io_concurrency Bruce Momjian
  • Re: hint in determining effective_io_concurrency Luca Ferrari
  • Re: hint in determining effective_io_concurrency Bruce Momjian
  • Re: hint in determining effective_io_concurrency Merlin Moncure
  • Re: hint in determining effective_io_concurrency Luca Ferrari
  • Re: hint in determining effective_io_concurrency Justin Pryzby
  • Re: hint in determining effective_io_concurrency Luca Ferrari
  • Re: hint in determining effective_io_concurrency Justin Pryzby
  • Re: hint in determining effective_io_concurrency Bruce Momjian
• Re: Planning performance problem (67626.278ms) David Rowley
  • Re: Planning performance problem (67626.278ms) Tom Lane
  • Re: Planning performance problem (67626.278ms) Manuel Weitzman
  • Re: Planning performance problem (67626.278ms) Manuel Weitzman
  • Re: Planning performance problem (67626.278ms) Tom Lane
  • Re: Planning performance problem (67626.278ms) Ranier Vilela
  • Re: Planning performance problem (67626.278ms) Tom Lane
  • Re: Planning performance problem (67626.278ms) Manuel Weitzman
  • Re: Planning performance problem (67626.278ms) Tom Lane
  • Re: Planning performance problem (67626.278ms) Manuel Weitzman
  • Re: Planning performance problem (67626.278ms) Tom Lane
  • Re: Planning performance problem (67626.278ms) Manuel Weitzman
  • Re: Planning performance problem (67626.278ms) Manuel Weitzman
  • Re: Planning performance problem (67626.278ms) David Rowley
• Re: OLEDB for PostgreSQL aditya desai
  • Re: OLEDB for PostgreSQL Pavan Pusuluri
• Most proper partitioning form on an integer column Il Mimo di Creta
  • Re: Most proper partitioning form on an integer column Justin Pryzby
• Is there a way to change current time? Warstone
  • Re: Is there a way to change current time? Bruce Momjian
  • Re: Is there a way to change current time? Justin Pryzby
  • Re: Is there a way to change current time? Tom Lane
  • Re: Is there a way to change current time? Pavel Stehule
  • Re: Is there a way to change current time? Eugene Pazhitnov
• Strange behavior once statistics are there Daniel Westermann (DWE)
  • Re: Strange behavior once statistics are there Tom Lane
  • Re: Strange behavior once statistics are there Daniel Westermann (DWE)
• Why is there a tenfold difference between Postgres's alleged query execution time and packet transmission time? Rollo Konig-Brock
  • Re: Why is there a tenfold difference between Postgres's alleged query execution time and packet transmission time? Tom Lane
• LWLocks by LockManager slowing large DB Paul Friedman
  • Re: LWLocks by LockManager slowing large DB Andres Freund
  • RE: LWLocks by LockManager slowing large DB Paul Friedman
  • Re: LWLocks by LockManager slowing large DB Andres Freund
  • RE: LWLocks by LockManager slowing large DB Paul Friedman
  • Re: LWLocks by LockManager slowing large DB Andres Freund

• Earlier messages
• Later messages