pgsql-performance  

Messages by Thread

• • Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries bruno da silva
  • Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries Andrew Dunstan
  • Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries bruno da silva
  • Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries Tom Lane
  • Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries bruno da silva
  • Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries Tom Lane
  • Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries bruno da silva
  • Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries Tom Lane
  • Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries bruno da silva
  • Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries Tom Lane
  • Re: PostgresSQL 9.5.21 very slow to connect and perform basic queries bruno da silva
• data consolidation: logical replication design considerations Rory Campbell-Lange
  • Re: data consolidation: logical replication design considerations Rick Otten
  • Re: data consolidation: logical replication design considerations Rory Campbell-Lange
  • Re: data consolidation: logical replication design considerations Rory Campbell-Lange
• Oracle_FDW table performance issue aditya desai
  • Re: Oracle_FDW table performance issue Justin Pryzby
  • Re: Oracle_FDW table performance issue aditya desai
  • Re: Oracle_FDW table performance issue Laurenz Albe
  • Re: Oracle_FDW table performance issue aditya desai
• functionality difference-performance postgreSQLv14-GCC-llvm-clang arjun shetty
• Occasional performance issue after changing table partitions Nathan Ward
  • Re: Occasional performance issue after changing table partitions Justin Pryzby
  • Re: Occasional performance issue after changing table partitions Nathan Ward
  • Re: Occasional performance issue after changing table partitions Justin Pryzby
  • Re: Occasional performance issue after changing table partitions Nathan Ward
  • Re: Occasional performance issue after changing table partitions Nathan Ward
  • Re: Occasional performance issue after changing table partitions Justin Pryzby
• Fluctuating performance of updates on small table with trigger Mikkel Lauritsen
  • Re: Fluctuating performance of updates on small table with trigger Justin Pryzby
• partition pruning only works for select but update James Pang (chaolpan)
  • Re: partition pruning only works for select but update Tom Lane
  • RE: partition pruning only works for select but update James Pang (chaolpan)
  • RE: partition pruning only works for select but update James Pang (chaolpan)
  • Re: partition pruning only works for select but update Justin Pryzby
  • Re: partition pruning only works for select but update Tom Lane
  • RE: partition pruning only works for select but update James Pang (chaolpan)
• reindex option for tuning load large data James Pang (chaolpan)
  • Re: reindex option for tuning load large data Vitalii Tymchyshyn
  • RE: reindex option for tuning load large data James Pang (chaolpan)
  • Re: reindex option for tuning load large data Jeff Janes
  • RE: reindex option for tuning load large data James Pang (chaolpan)
  • Re: reindex option for tuning load large data I. V.
• Missed query planner optimization: `n in (select q)` -> `n in (q)` Josh
  • Re: Missed query planner optimization: `n in (select q)` -> `n in (q)` David G. Johnston
• Adding non-selective key to jsonb query @> reduces performance? Marcin Krupowicz
  • Re: Adding non-selective key to jsonb query @> reduces performance? Tom Lane
• Strange behavior of limit clause in complex query Paulo Silva
  • Re: Strange behavior of limit clause in complex query Ranier Vilela
  • Re: Strange behavior of limit clause in complex query Paulo Silva
  • Re: Strange behavior of limit clause in complex query Justin Pryzby
• Query is taking too long i intermittent Mayank Kandari
  • Re: Query is taking too long i intermittent Justin Pryzby
  • Re: Query is taking too long i intermittent Tom Lane
  • Re: Query is taking too long i intermittent Mayank Kandari
• Logical reads Goti
• REINDEXdb performance degrading gradually PG13.4 Praneel Devisetty
  • REINDEXdb performance degrading gradually PG13.4 David G. Johnston
  • Re: REINDEXdb performance degrading gradually PG13.4 Michael Paquier
  • Re: REINDEXdb performance degrading gradually PG13.4 Praneel Devisetty
  • Re: REINDEXdb performance degrading gradually PG13.4 Jeff Janes
• postgres backend process hang on " D " state James Pang (chaolpan)
  • Re: postgres backend process hang on " D " state Ranier Vilela
  • Re: postgres backend process hang on " D " state Justin Pryzby
  • RE: postgres backend process hang on " D " state James Pang (chaolpan)
  • Re: postgres backend process hang on " D " state Justin Pryzby
  • RE: postgres backend process hang on " D " state James Pang (chaolpan)
  • Re: postgres backend process hang on " D " state Tom Lane
  • RE: postgres backend process hang on " D " state James Pang (chaolpan)
  • RE: postgres backend process hang on " D " state James Pang (chaolpan)
• rows selectivity overestimate for @> operator for arrays Alexey Ermakov
  • Re: rows selectivity overestimate for @> operator for arrays Tom Lane
  • Re: rows selectivity overestimate for @> operator for arrays Jeff Janes
• How to monitor Postgres real memory usage 徐志宇徐
  • Re: How to monitor Postgres real memory usage Justin Pryzby
  • Re: How to monitor Postgres real memory usage 徐志宇徐
  • Re: How to monitor Postgres real memory usage 徐志宇徐
  • Re: How to monitor Postgres real memory usage Justin Pryzby
  • Re: How to monitor Postgres real memory usage 徐志宇徐
  • Re: How to monitor Postgres real memory usage Justin Pryzby
  • Re: How to monitor Postgres real memory usage Justin Pryzby
• Selecting RAM and CPU based on max_connections aditya desai
  • Re: Selecting RAM and CPU based on max_connections Andreas Kretschmer
  • Re: Selecting RAM and CPU based on max_connections Laurenz Albe
  • Re: Selecting RAM and CPU based on max_connections aditya desai
  • Re: Selecting RAM and CPU based on max_connections Ganesh Korde
• Need help on Query Tunning and Not using the Index Scan Kumar, Mukesh
  • Re: Need help on Query Tunning and Not using the Index Scan Laurenz Albe
• DB connection issue suggestions Sudhir Guna
  • Re: DB connection issue suggestions MichaelDBA Vitale
  • Re: DB connection issue suggestions Sudhir Guna
  • Re: DB connection issue suggestions Ranier Vilela
  • Re: DB connection issue suggestions Justin Pryzby
  • Re: DB connection issue suggestions Sudhir Guna
  • Re: DB connection issue suggestions Justin Pryzby
  • Re: DB connection issue suggestions Sudhir Guna
  • Re: DB connection issue suggestions Justin Pryzby
  • Re: DB connection issue suggestions Ranier Vilela
  • Re: DB connection issue suggestions Sudhir Guna
  • Re: DB connection issue suggestions Sudhir Guna
  • Re: DB connection issue suggestions Laurenz Albe
  • Re: DB connection issue suggestions Anbazhagan M
• Why is there a Sort after an Index Only Scan? André Hänsel
  • Re: Why is there a Sort after an Index Only Scan? Jeff Janes
  • Re: Why is there a Sort after an Index Only Scan? David Rowley
  • RE: Why is there a Sort after an Index Only Scan? André Hänsel
  • Re: Why is there a Sort after an Index Only Scan? Tom Lane
• Window partial fetch optimization Levi Aul
  • Re: Window partial fetch optimization David Rowley
  • Re: Window partial fetch optimization Jeff Janes
• Useless memoize path generated for unique join on primary keys Benjamin Coutu
  • Re: Useless memoize path generated for unique join on primary keys David Rowley
  • Re: Useless memoize path generated for unique join on primary keys Benjamin Coutu
  • Re: Useless memoize path generated for unique join on primary keys David Rowley
• FATAL: canceling authentication due to timeout aditya desai
• LISTEN NOTIFY sometimes huge delay Peter Eser HEUFT [Germany]
  • Re: LISTEN NOTIFY sometimes huge delay Tom Lane
• Unworkable plan above certain row count André Hänsel
  • Re: Unworkable plan above certain row count Tom Lane
• Fwd: Array of integer indexed nested-loop semi join Mickael van der Beek
  • Re: Array of integer indexed nested-loop semi join Jeff Janes
  • Re: Array of integer indexed nested-loop semi join Mickael van der Beek
  • Re: Array of integer indexed nested-loop semi join Mickael van der Beek
  • Re: Array of integer indexed nested-loop semi join Jeff Janes
  • Re: Array of integer indexed nested-loop semi join Mickael van der Beek
  • Re: Array of integer indexed nested-loop semi join Jeff Janes
  • Re: Array of integer indexed nested-loop semi join Mickael van der Beek
• Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected. Emil Iggland
  • Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected. Tom Lane
  • Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected. Emil Iggland
  • Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected. David Rowley
  • Re: Performance differential when 0 values present vs when 1 values present. Planner return 52k rows when 0 expected. Emil Iggland
• significant jump in sql statement timing for on server vs a remote connection Sbob
  • Re: significant jump in sql statement timing for on server vs a remote connection Justin Pryzby
  • Re: significant jump in sql statement timing for on server vs a remote connection Jeff Janes
  • Re: significant jump in sql statement timing for on server vs a remote connection Sbob
  • Re: significant jump in sql statement timing for on server vs a remote connection Ranier Vilela
• How to find all SQLs executed by a transaction id? Patil, Ravi
• How to find the final transformed query in postgresql Goti
  • Re: How to find the final transformed query in postgresql Tom Lane
  • Re: How to find the final transformed query in postgresql Goti
• Query Planner not taking advantage of HASH PARTITION Benjamin Tingle
  • Re: Query Planner not taking advantage of HASH PARTITION Tom Lane
  • Re: Query Planner not taking advantage of HASH PARTITION Benjamin Tingle
  • Re: Query Planner not taking advantage of HASH PARTITION Tom Lane
  • Re: Query Planner not taking advantage of HASH PARTITION Alvaro Herrera
  • Re: Query Planner not taking advantage of HASH PARTITION Benjamin Tingle
  • Re: Query Planner not taking advantage of HASH PARTITION Justin Pryzby
• Query Tunning related to function Kumar, Mukesh
  • Re: Query Tunning related to function Ranier Vilela
  • RE: Query Tunning related to function Kumar, Mukesh
  • RE: Query Tunning related to function Michel SALAIS
  • RE: Query Tunning related to function Kumar, Mukesh
  • Re: Query Tunning related to function Bhupendra Babu
  • RE: Query Tunning related to function Kumar, Mukesh
  • RE: Query Tunning related to function Kumar, Mukesh
  • Re: Query Tunning related to function David G. Johnston
  • Re: Query Tunning related to function Justin Pryzby
• SQL performance issue after migration from Oracle to Aurora postgres Goti
  • Re: SQL performance issue after migration from Oracle to Aurora postgres Andrew Dunstan
• Performance for SQL queries on Azure PostgreSQL PaaS instance Kumar, Mukesh
  • Re: Performance for SQL queries on Azure PostgreSQL PaaS instance Frits Jalvingh
  • Re: Performance for SQL queries on Azure PostgreSQL PaaS instance Tomas Vondra
  • Re: Performance for SQL queries on Azure PostgreSQL PaaS instance Laurenz Albe
  • RE: Performance for SQL queries on Azure PostgreSQL PaaS instance Kumar, Mukesh
  • Re: Performance for SQL queries on Azure PostgreSQL PaaS instance andrew cooke
  • Re: Performance for SQL queries on Azure PostgreSQL PaaS instance overland
• Slow Planning Times Saurabh Sehgal
  • Re: Slow Planning Times Saurabh Sehgal
  • Re: Slow Planning Times David G. Johnston
  • Re: Slow Planning Times Saurabh Sehgal
  • Re: Slow Planning Times Tom Lane
  • Re: Slow Planning Times Saurabh Sehgal
• Postgresql TPS Bottleneck wakandavision
  • Re: Postgresql TPS Bottleneck Guillaume Cottenceau
  • Re: Postgresql TPS Bottleneck MichaelDBA
  • Re: Postgresql TPS Bottleneck Tomas Vondra
  • Re: Postgresql TPS Bottleneck wakandavision
  • Re: Postgresql TPS Bottleneck Jeff Janes
  • Re: Postgresql TPS Bottleneck wakandavision
  • Re: Postgresql TPS Bottleneck Benedict Holland
  • Re: Postgresql TPS Bottleneck Mladen Gogala
• HIGH IO and Less CPU utilization Rambabu g
  • Re: HIGH IO and Less CPU utilization Justin Pryzby
  • Re: HIGH IO and Less CPU utilization Rambabu g
  • Re: HIGH IO and Less CPU utilization Justin Pryzby
  • Re: HIGH IO and Less CPU utilization Rambabu g
  • Re: HIGH IO and Less CPU utilization Justin Pryzby
  • Re: HIGH IO and Less CPU utilization Rambabu g
  • Re: HIGH IO and Less CPU utilization Mladen Gogala
• View taking time to show records Kumar, Mukesh
  • Re: View taking time to show records aditya desai
  • Re: View taking time to show records hubert depesz lubaczewski
  • Re: View taking time to show records Laurenz Albe
  • RE: View taking time to show records Kumar, Mukesh
  • Re: View taking time to show records Laurenz Albe
• Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join Prajna Shetty
  • Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join Justin Pryzby
  • Re: Performance issue post upgrade on Version 13 - Incorrect Estimation Cost choosing Hash Aggregate-Nested Left Loop Join Tomas Vondra
• High process memory consumption when running sort Shai Shapira

• Earlier messages
• Later messages