pgsql-performance  

Messages by Thread

• PostgreSQL performance problem moving from 9.6.17 to 12.3 Kenneth Marshall
  • Re: PostgreSQL performance problem moving from 9.6.17 to 12.3 Tom Lane
• Date vs Timestamp without timezone Partition Key Cedric Leong
  • Re: Date vs Timestamp without timezone Partition Key Tom Lane
  • Re: Date vs Timestamp without timezone Partition Key Cedric Leong
  • Re: Date vs Timestamp without timezone Partition Key David Rowley
  • Re: Date vs Timestamp without timezone Partition Key Cedric Leong
  • Re: Date vs Timestamp without timezone Partition Key David Rowley
  • Re: Date vs Timestamp without timezone Partition Key Cedric Leong
• Strategy for materialisation and centralisation of data Rory Campbell-Lange
• Request to help on Query improvement suggestion. devchef2020 d
  • Re: Request to help on Query improvement suggestion. Laurenz Albe
  • Re: Request to help on Query improvement suggestion. Marlene Villanueva
• Request to help on GIS Query improvement suggestion. postggen2020 s
  • Re: Request to help on GIS Query improvement suggestion. Michael Lewis
• Suggestion to improve query performance for GIS query. postgann2020 s
  • Re: Suggestion to improve query performance for GIS query. David G. Johnston
  • Re: Suggestion to improve query performance for GIS query. Mohammed Afsar
  • Re: Suggestion to improve query performance for GIS query. postgann2020 s
• Suggestion to improve query performance of data validation in proc. postgann2020 s
• Suggestion on index creation for TEXT data field postgann2020 s
  • Re: Suggestion on index creation for TEXT data field David G. Johnston
  • Re: Suggestion on index creation for TEXT data field postgann2020 s
  • Re: Suggestion on index creation for TEXT data field David G. Johnston
  • Re: Suggestion on index creation for TEXT data field postgann2020 s
  • Re: Suggestion on index creation for TEXT data field Adrian Klaver
• Suggestion on table analyze postgann2020 s
  • Re: Suggestion on table analyze Adrian Klaver
  • Re: Suggestion on table analyze postgann2020 s
• Suggestion to improve query performance. postgann2020 s
• OOM Killer kills PostgreSQL Piotr Włodarczyk
  • Re: OOM Killer kills PostgreSQL Laurenz Albe
  • Re: OOM Killer kills PostgreSQL Piotr Włodarczyk
  • Re: OOM Killer kills PostgreSQL Fabio Pardi
  • Re: OOM Killer kills PostgreSQL Justin Pryzby
  • Re: OOM Killer kills PostgreSQL Stephen Frost
• Re: Execution time from >1s -> 80m+ when extra columns added in SELECT for sub-query Pavel Stehule
  • Re: Execution time from >1s -> 80m+ when extra columns added in SELECT for sub-query A Guy Named Ryan
  • Re: Execution time from >1s -> 80m+ when extra columns added in SELECT for sub-query Tom Lane
• Plan not skipping unnecessary inner join Matthew Nelson
  • Re: Plan not skipping unnecessary inner join David Wheeler
  • Re: Plan not skipping unnecessary inner join Matthew Nelson
  • Re: Plan not skipping unnecessary inner join Ranier Vilela
  • Re: Plan not skipping unnecessary inner join Justin Pryzby
  • Re: Plan not skipping unnecessary inner join Ranier Vilela
• pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. samhitha g
  • Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. David G. Johnston
  • Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. Avinash Kumar
  • Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. Rory Campbell-Lange
  • Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. Avinash Kumar
  • Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. Laurenz Albe
  • Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. Avinash Kumar
  • Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. Laurenz Albe
  • Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. Avinash Kumar
  • Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. MichaelDBA
  • Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. Jeff Janes
  • Re: pg_attribute, pg_class, pg_depend grow huge in count and size with multiple tenants. Jeff Janes
• AutoVacuum and growing transaction XID's github kran
  • Re: AutoVacuum and growing transaction XID's Michael Lewis
  • Re: AutoVacuum and growing transaction XID's github kran
  • Re: AutoVacuum and growing transaction XID's github kran
  • Re: AutoVacuum and growing transaction XID's David Rowley
  • Re: AutoVacuum and growing transaction XID's github kran
  • Re: AutoVacuum and growing transaction XID's Michael Lewis
  • Re: AutoVacuum and growing transaction XID's github kran
  • Re: AutoVacuum and growing transaction XID's David Rowley
  • Re: AutoVacuum and growing transaction XID's github kran
• Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) Amarendra Konda
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) Adrian Klaver
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) David G. Johnston
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) Amarendra Konda
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) Amarendra Konda
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) Amarendra Konda
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) Virendra Kumar
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) David G. Johnston
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) David Rowley
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) Adrian Klaver
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) David G. Johnston
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) Tom Lane
  • Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) Amarendra Konda
• Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join Steve Pritchard
  • Re: Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join Justin Pryzby
  • Re: Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join Jeff Janes
  • Re: Inaccurate Rows estimate for "Bitmap And" causes Planner to choose wrong join Steve Pritchard
• good book or any other resources for Postgresql Bhupendra Babu
  • Re: good book or any other resources for Postgresql Michael Lewis
  • Re: good book or any other resources for Postgresql Craig Jackson
  • Re: good book or any other resources for Postgresql Bhupendra Babu
• 600 million rows of data. Bad hardware or need partitioning? Arya F
  • Re: 600 million rows of data. Bad hardware or need partitioning? Michael Lewis
  • Re: 600 million rows of data. Bad hardware or need partitioning? Arya F
  • Re: 600 million rows of data. Bad hardware or need partitioning? David Rowley
  • Re: 600 million rows of data. Bad hardware or need partitioning? Arya F
  • Re: 600 million rows of data. Bad hardware or need partitioning? Justin Pryzby
  • Re: 600 million rows of data. Bad hardware or need partitioning? Arya F
  • Re: 600 million rows of data. Bad hardware or need partitioning? Justin Pryzby
  • Re: 600 million rows of data. Bad hardware or need partitioning? Arya F
• Please help! Query jumps from 1s -> 4m James Thompson
  • Re: Please help! Query jumps from 1s -> 4m Justin Pryzby
  • Re: Please help! Query jumps from 1s -> 4m Justin Pryzby
  • Re: Please help! Query jumps from 1s -> 4m Justin Pryzby
  • Re: Please help! Query jumps from 1s -> 4m James Thompson
  • Re: Please help! Query jumps from 1s -> 4m Justin Pryzby
  • Re: Please help! Query jumps from 1s -> 4m Tom Lane
  • Re: Please help! Query jumps from 1s -> 4m James Thompson
  • Re: Please help! Query jumps from 1s -> 4m James Thompson
  • Re: Please help! Query jumps from 1s -> 4m Laurenz Albe
  • Re: Please help! Query jumps from 1s -> 4m David Rowley
• Best partition type for billions of addresses Arya F
  • Re: Best partition type for billions of addresses Justin Pryzby
  • Re: Best partition type for billions of addresses Stephen Frost
  • Re: Best partition type for billions of addresses Arya F
  • Re: Best partition type for billions of addresses Stephen Frost
• NUMA settings Marc Rechté
  • Re: NUMA settings Laurenz Albe
  • Re: NUMA settings Andres Freund
  • Re: NUMA settings Marc Rechté
  • Re: NUMA settings Laurenz Albe
  • Re: NUMA settings Marc Rechté
  • Re: NUMA settings Laurenz Albe
• Recursive query slow on strange conditions Jean-Christophe Boggio
  • Re: Recursive query slow on strange conditions Justin Pryzby
  • Re: Recursive query slow on strange conditions Andreas Joseph Krogh
  • Re: Recursive query slow on strange conditions Jean-Christophe Boggio
  • Re: Recursive query slow on strange conditions Jean-Christophe Boggio
  • Re: Recursive query slow on strange conditions David G. Johnston
  • Re: Recursive query slow on strange conditions Jean-Christophe Boggio
• The query plan get all columns but I'm using only one column. Moises Lopez
  • Re: The query plan get all columns but I'm using only one column. Tom Lane
  • Re: The query plan get all columns but I'm using only one column. Michael Lewis
  • Re: The query plan get all columns but I'm using only one column. Michael Lewis
  • Re: The query plan get all columns but I'm using only one column. Michael Lewis
  • Re: The query plan get all columns but I'm using only one column. Moises Lopez
• PostgreSQL does not choose my indexes well Arcadio Ortega Reinoso
  • Re: PostgreSQL does not choose my indexes well Thomas Kellerer
  • Re: PostgreSQL does not choose my indexes well David G. Johnston
  • Re: PostgreSQL does not choose my indexes well Tom Lane
  • Re: PostgreSQL does not choose my indexes well Michael Lewis
  • Re: PostgreSQL does not choose my indexes well Tom Lane
  • Re: PostgreSQL does not choose my indexes well David G. Johnston
  • Re: PostgreSQL does not choose my indexes well Stephen Frost
  • Re: PostgreSQL does not choose my indexes well Stephen Frost
  • Re: PostgreSQL does not choose my indexes well Tom Lane
  • Re: PostgreSQL does not choose my indexes well Stephen Frost
  • Re: PostgreSQL does not choose my indexes well Tom Lane
  • Re: PostgreSQL does not choose my indexes well David G. Johnston
  • Re: PostgreSQL does not choose my indexes well Tom Lane
  • Re: PostgreSQL does not choose my indexes well Arcadio Ortega Reinoso
  • Re: PostgreSQL does not choose my indexes well Jeff Janes
  • Re: PostgreSQL does not choose my indexes well Stephen Frost
  • Re: PostgreSQL does not choose my indexes well Tom Lane
  • Re: PostgreSQL does not choose my indexes well Stephen Frost
  • Re: PostgreSQL does not choose my indexes well Arcadio Ortega Reinoso
  • Re: PostgreSQL does not choose my indexes well Jeff Janes
• Using unlogged tables for web sessions Stephen Carboni
• Duplicate WHERE condition changes performance and plan singh...@gmail.com
  • Re: Duplicate WHERE condition changes performance and plan David Rowley
  • Re: Duplicate WHERE condition changes performance and plan singh...@gmail.com
  • Re: Duplicate WHERE condition changes performance and plan Justin Pryzby
  • Re: Duplicate WHERE condition changes performance and plan singh...@gmail.com
  • Re: Duplicate WHERE condition changes performance and plan singh...@gmail.com
  • Re: Duplicate WHERE condition changes performance and plan Michael Lewis
• High kswapd Don Seiler
  • Re: High kswapd Justin Pryzby
  • Re: High kswapd Don Seiler
  • Re: High kswapd Justin Pryzby
  • Re: High kswapd Don Seiler
• High insert rate server, unstable insert latency and load peaks with buffer_content and XidGenLock LWlocks with Postgresql 12 version Maxim Boguk
  • Re: High insert rate server, unstable insert latency and load peaks with buffer_content and XidGenLock LWlocks with Postgresql 12 version Justin Pryzby
  • Re: High insert rate server, unstable insert latency and load peaks with buffer_content and XidGenLock LWlocks with Postgresql 12 version Maxim Boguk
• PostgreSQL DBA consulting daya airody
  • Re: PostgreSQL DBA consulting Justin Pryzby
  • Re: PostgreSQL DBA consulting Amol Tarte
• Re: slow query Michael Christofides
  • 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
• Postgres not using index on views Rick Vincent
  • Re: Postgres not using index on views Justin Pryzby
  • Re: Postgres not using index on views Tom Lane
  • RE: Postgres not using index on views Rick Vincent
  • Re: Postgres not using index on views Thomas Kellerer
  • RE: Postgres not using index on views Rick Vincent
  • Postgres not using index on views David G. Johnston
  • RE: Postgres not using index on views Rick Vincent
  • RE: Postgres not using index on views Rick Vincent
  • RE: Postgres not using index on views Rick Vincent
  • Re: Postgres not using index on views Thomas Kellerer
  • Re: Postgres not using index on views Laurenz Albe
• Re: Postgresql 12, 512 partition by hash. Slow select Tom Lane
  • Re: Postgresql 12, 512 partition by hash. Slow select Arya F
  • Re: Postgresql 12, 512 partition by hash. Slow select Neil

• Later messages