pgsql-performance  

Messages by Thread

• • Re: Query Performance / Planner estimate off Mats Olsen
  • Re: Query Performance / Planner estimate off Victor Yegorov
  • Re: Query Performance / Planner estimate off Mats Olsen
  • Re: Query Performance / Planner estimate off Victor Yegorov
  • Re: Query Performance / Planner estimate off Mats Olsen
  • Re: Query Performance / Planner estimate off Sushant Pawar
  • Re: Query Performance / Planner estimate off Mats Olsen
  • Re: Query Performance / Planner estimate off Mats Olsen
  • Re: Query Performance / Planner estimate off Sebastian Dressler
  • Re: Query Performance / Planner estimate off Mats Olsen
  • Re: Query Performance / Planner estimate off Michael Lewis
  • Re: Query Performance / Planner estimate off Mats Olsen
  • Re: Query Performance / Planner estimate off Sebastian Dressler
  • Re: Query Performance / Planner estimate off Mats Olsen
  • Re: Query Performance / Planner estimate off Justin Pryzby
  • Re: Query Performance / Planner estimate off Mats Olsen
  • Re: Query Performance / Planner estimate off Justin Pryzby
  • Re: Query Performance / Planner estimate off Mats Olsen
• CPU Consuming query. Sequential scan despite indexing. aditya desai
  • Re: CPU Consuming query. Sequential scan despite indexing. Michael Lewis
  • Re: CPU Consuming query. Sequential scan despite indexing. Michael Lewis
  • Re: CPU Consuming query. Sequential scan despite indexing. aditya desai
  • Re: CPU Consuming query. Sequential scan despite indexing. aditya desai
  • Re: CPU Consuming query. Sequential scan despite indexing. aditya desai
  • Re: CPU Consuming query. Sequential scan despite indexing. David G. Johnston
  • Re: CPU Consuming query. Sequential scan despite indexing. aditya desai
  • Re: CPU Consuming query. Sequential scan despite indexing. Laurenz Albe
  • Re: CPU Consuming query. Sequential scan despite indexing. aditya desai
  • Re: CPU Consuming query. Sequential scan despite indexing. aditya desai
• Poor Performance running Django unit tests after upgrading from 10.6 Roger Hunwicks
  • Re: Poor Performance running Django unit tests after upgrading from 10.6 Laurenz Albe
  • Re: Poor Performance running Django unit tests after upgrading from 10.6 Andrew Dunstan
  • Re: Poor Performance running Django unit tests after upgrading from 10.6 Tom Lane
• Slow Query Parth Shah
  • Re: Slow Query Michael Lewis
  • Re: Slow Query Parth Shah
  • Re: Slow Query Michael Lewis
  • slow query Ayub Khan
  • Re: slow query Christophe Pettus
  • Re: slow query Ayub Khan
  • Re: slow query Jeff Janes
  • Re: slow query Tom Lane
  • Re: slow query Ayub Khan
  • Re: slow query Ayub Khan
• Indexing an XMLTABLE query? Kanninen Anssi EXT
  • Re: Indexing an XMLTABLE query? Pavel Stehule
• Too many waits on extension of relation avinash varma
  • Re: Too many waits on extension of relation Michael Lewis
  • Re: Too many waits on extension of relation Sushant Pawar
  • Re: Too many waits on extension of relation MichaelDBA
  • Re: Too many waits on extension of relation avinash varma
  • Re: Too many waits on extension of relation Laurenz Albe
• SSL connection getting rejected on AWS RDS aditya desai
  • Re: SSL connection getting rejected on AWS RDS Hannah Huang
  • Re: SSL connection getting rejected on AWS RDS aditya desai
  • Re: SSL connection getting rejected on AWS RDS Hannah Huang
• Is it possible to specify minimum number of rows planner should consider? Timothy Garnett
  • Re: Is it possible to specify minimum number of rows planner should consider? Tom Lane
  • Re: Is it possible to specify minimum number of rows planner should consider? Matthew Bellew
  • Re: Is it possible to specify minimum number of rows planner should consider? Timothy Garnett
• How to encrypt database password in pgpass or unix file to run batch jobs through shell script aditya desai
  • Re: How to encrypt database password in pgpass or unix file to run batch jobs through shell script Bruce Momjian
• Performance issue when we use policies for Row Level Security along with functions Gopisetty, Ramesh
  • Re: Performance issue when we use policies for Row Level Security along with functions luis . roberto
  • Re: Performance issue when we use policies for Row Level Security along with functions Tom Lane
  • Re: Performance issue when we use policies for Row Level Security along with functions Gopisetty, Ramesh
  • Performance issue when we use policies for Row Level Security along with functions David G. Johnston
• Single column vs composite partial index Nagaraj Raj
  • Re: Single column vs composite partial index Justin Pryzby
  • Re: Single column vs composite partial index Nagaraj Raj
  • Re: Single column vs composite partial index Michael Lewis
• autoanalyze creates bad plan, manual analyze fixes it? Robert Treat
  • Re: autoanalyze creates bad plan, manual analyze fixes it? Justin Pryzby
  • Re: autoanalyze creates bad plan, manual analyze fixes it? Robert Treat
  • Re: autoanalyze creates bad plan, manual analyze fixes it? Pavel Stehule
• Performance Issue (Not using Index when joining two tables). Gopisetty, Ramesh
  • Re: Performance Issue (Not using Index when joining two tables). Tomas Vondra
  • Re: Performance Issue (Not using Index when joining two tables). Tom Lane
  • Re: Performance Issue (Not using Index when joining two tables). Michael Lewis
  • Re: Performance Issue (Not using Index when joining two tables). Gopisetty, Ramesh
  • Re: Performance Issue (Not using Index when joining two tables). Tom Lane
• AWS RDS PostgreSQL CPU Spiking to 100% aditya desai
  • Re: AWS RDS PostgreSQL CPU Spiking to 100% Pavel Stehule
  • Re: AWS RDS PostgreSQL CPU Spiking to 100% Jeff Janes
  • Re: AWS RDS PostgreSQL CPU Spiking to 100% aditya desai
  • Re: AWS RDS PostgreSQL CPU Spiking to 100% Prince Pathria
  • Re: AWS RDS PostgreSQL CPU Spiking to 100% aditya desai
• Query Performance in bundled requests Dirk Krautschick
  • Re: Query Performance in bundled requests Justin Pryzby
• Query performance issue Nagaraj Raj
  • Re: Query performance issue Thomas Kellerer
  • Re: Query performance issue Nagaraj Raj
  • Re: Query performance issue Michael Lewis
  • Re: Query performance issue Michael Lewis
  • Re: Query performance issue Nagaraj Raj
  • Re: Query performance issue Michael Lewis
  • Re: Query performance issue Nagaraj Raj
  • Re: Query performance issue David Rowley
  • Re: Query performance issue Michael Lewis
  • Re: Query performance issue Nagaraj Raj
  • AW: Query performance issue Dirk Krautschick
  • Re: Query performance issue Tomas Vondra
  • Query performance issue Nagaraj Raj
  • Re: Query performance issue Justin Pryzby
  • Re: Query performance issue Tomas Vondra
  • Re: Query performance issue Michael Lewis
  • Query performance issue Dheeraj Sonawane
  • Re: Query performance issue Tom Lane
• sizing / capacity planning tipps related to expected request or transactions per second Dirk Krautschick
  • Re: sizing / capacity planning tipps related to expected request or transactions per second MichaelDBA
  • Re: sizing / capacity planning tipps related to expected request or transactions per second Pavel Stehule
• CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Jim Jarvie
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Michael Lewis
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Jim Jarvie
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Henrique Montenegro
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Michael Lewis
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Michael Lewis
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Jim Jarvie
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Michael Lewis
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Jim Jarvie
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Michael Lewis
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Jim Jarvie
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Michael Lewis
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED David Rowley
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Raj
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Jim Jarvie
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED David Rowley
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Alvaro Herrera
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Jeff Janes
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Laurenz Albe
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Thomas Munro
  • Re: CPU hogged by concurrent SELECT..FOR UPDATE SKIP LOCKED Jim Jarvie
• Replication lag due to lagging restart_lsn Satyam Shekhar
  • Re: Replication lag due to lagging restart_lsn Kyotaro Horiguchi
  • Re: Replication lag due to lagging restart_lsn Kiran Singh
  • Re: Replication lag due to lagging restart_lsn milist ujang
  • Re: Replication lag due to lagging restart_lsn milist ujang
• Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query Ken Tanzer
  • Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query Justin Pryzby
  • Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query Ken Tanzer
  • Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query Justin Pryzby
  • Re: Query takes way longer with LIMIT, and EXPLAIN takes way longer than actual query Jeff Janes
• Hstore index for full text search Burhan Akbulut
  • Re: Hstore index for full text search Michael Lewis
  • Re: Hstore index for full text search Tom Lane
  • Re: Hstore index for full text search Michael Lewis
  • Re: Hstore index for full text search Tom Lane
• Problems with Multixacts LWLocks Czarek
• Too few rows expected by Planner on partitioned tables Julian Wolf
  • Re: Too few rows expected by Planner on partitioned tables Justin Pryzby
  • Re: Too few rows expected by Planner on partitioned tables Julian Wolf
  • Re: Too few rows expected by Planner on partitioned tables Justin Pryzby
  • Re: Too few rows expected by Planner on partitioned tables Justin Pryzby
  • Re: Too few rows expected by Planner on partitioned tables Julian Wolf
  • Re: Too few rows expected by Planner on partitioned tables Julian Wolf
  • Re: Too few rows expected by Planner on partitioned tables Michael Lewis
• Re: Same query taking less time in low configuration machine Justin Pryzby
  • Re: Same query taking less time in low configuration machine Vishwa Kalyankar
  • Re: Same query taking less time in low configuration machine Justin Pryzby
  • Re: Same query taking less time in low configuration machine Vishwa Kalyankar
• Sudden insert performance degradation Henrique Montenegro
  • Re: Sudden insert performance degradation Sebastian Dressler
  • Re: Sudden insert performance degradation Henrique Montenegro
  • Re: Sudden insert performance degradation Sebastian Dressler
  • Re: Sudden insert performance degradation Henrique Montenegro
  • Re: Sudden insert performance degradation Michael Lewis
  • Re: Sudden insert performance degradation Henrique Montenegro
  • Re: Sudden insert performance degradation Jeff Janes
  • Re: Sudden insert performance degradation Henrique Montenegro
  • Re: Sudden insert performance degradation Henrique Montenegro
  • Re: Sudden insert performance degradation Sebastian Dressler
  • Re: Sudden insert performance degradation Henrique Montenegro
  • Re: Sudden insert performance degradation Henrique Montenegro
  • Re: Sudden insert performance degradation Justin Pryzby
• Re: Request to help on Query improvement suggestion. Marlene Villanueva
• Is there a known bug with SKIP LOCKED and "tuple to be locked was already moved to another partition due to concurrent update"? Gunther Schadow
  • Re: Is there a known bug with SKIP LOCKED and "tuple to be locked was already moved to another partition due to concurrent update"? Jim Jarvie
  • Re: Is there a known bug with SKIP LOCKED and "tuple to be locked was already moved to another partition due to concurrent update"? Kamil Dziedzic
  • Re: Is there a known bug with SKIP LOCKED and "tuple to be locked was already moved to another partition due to concurrent update"? Michael Lewis
  • Re: Is there a known bug with SKIP LOCKED and "tuple to be locked was already moved to another partition due to concurrent update"? Kamil Dziedzic
• Recommended value for pg_test_fsync Nikhil Shetty
  • Re: Recommended value for pg_test_fsync Bruce Momjian
  • Re: Recommended value for pg_test_fsync Nikhil Shetty
  • Re: Recommended value for pg_test_fsync Bruce Momjian
  • Re: Recommended value for pg_test_fsync Nikhil Shetty
  • Re: Recommended value for pg_test_fsync Jeff Janes
  • Re: Recommended value for pg_test_fsync Jeff Janes
  • Re: Recommended value for pg_test_fsync Nikhil Shetty
  • Re: Recommended value for pg_test_fsync Nikhil Shetty
  • Re: Recommended value for pg_test_fsync Haroldo Kerry
  • Re: Recommended value for pg_test_fsync Nikhil Shetty
  • Re: Recommended value for pg_test_fsync Nikhil Shetty
  • Re: Recommended value for pg_test_fsync Bruce Momjian
• Re: PostgreSQL 12.3 slow index scan chosen Kenneth Marshall
  • Re: PostgreSQL 12.3 slow index scan chosen Tom Lane
  • Re: PostgreSQL 12.3 slow index scan chosen Tom Lane
  • Re: PostgreSQL 12.3 slow index scan chosen Kenneth Marshall
  • Re: PostgreSQL 12.3 slow index scan chosen Alvaro Herrera
  • Re: PostgreSQL 12.3 slow index scan chosen Kenneth Marshall
  • Re: PostgreSQL 12.3 slow index scan chosen Tom Lane

• Later messages