pgsql-performance  

Messages by Thread

• • Re: LWLocks by LockManager slowing large DB Tom Lane
  • Re: LWLocks by LockManager slowing large DB Andres Freund
  • Re: LWLocks by LockManager slowing large DB Tom Lane
  • Re: LWLocks by LockManager slowing large DB Andres Freund
  • Re: LWLocks by LockManager slowing large DB Alvaro Herrera
  • RE: LWLocks by LockManager slowing large DB Paul Friedman
  • Re: LWLocks by LockManager slowing large DB Nikolay Samokhvalov
  • RE: LWLocks by LockManager slowing large DB Paul Friedman
• INSERTS waiting with wait_event is "transactionid" Nagaraj Raj
  • Re: INSERTS waiting with wait_event is "transactionid" Laurenz Albe
  • Re: INSERTS waiting with wait_event is "transactionid" Nagaraj Raj
• str_aggr function not wokring aditya desai
  • RE: str_aggr function not wokring Patrick FICHE
  • Re: str_aggr function not wokring aditya desai
  • Re: str_aggr function not wokring aditya desai
• procedure using CURSOR to insert is extremely slow Szalontai Zoltán
  • Re: procedure using CURSOR to insert is extremely slow HER
  • RE: procedure using CURSOR to insert is extremely slow Szalontai Zoltán
  • Re: procedure using CURSOR to insert is extremely slow Milos Babic
  • RE: procedure using CURSOR to insert is extremely slow Szalontai Zoltán
  • RE: procedure using CURSOR to insert is extremely slow Mike Sofen
  • Re: procedure using CURSOR to insert is extremely slow Milos Babic
  • RE: procedure using CURSOR to insert is extremely slow Szalontai Zoltán
• select count(*) is slow aditya desai
  • Re: select count(*) is slow Tom Lane
  • Re: select count(*) is slow aditya desai
  • Re: select count(*) is slow Andrew Dunstan
  • Re: select count(*) is slow aditya desai
• Substitute for synonym in Oracle after migration to postgres aditya desai
  • Re: Substitute for synonym in Oracle after migration to postgres Laurenz Albe
  • Re: Substitute for synonym in Oracle after migration to postgres hubert depesz lubaczewski
  • Re: Substitute for synonym in Oracle after migration to postgres aditya desai
• PosgtgreSQL hot standby reading WAL from muli-attached volume? Gunther Schadow
• SHARED LOCKS , EXCLUSIVE LOCKS, ACCESS EXCLUSIVE LOCKS aditya desai
  • Re: SHARED LOCKS , EXCLUSIVE LOCKS, ACCESS EXCLUSIVE LOCKS Amine Tengilimoglu
  • Re: SHARED LOCKS , EXCLUSIVE LOCKS, ACCESS EXCLUSIVE LOCKS Justin Pryzby
  • Re: SHARED LOCKS , EXCLUSIVE LOCKS, ACCESS EXCLUSIVE LOCKS aditya desai
  • Re: SHARED LOCKS , EXCLUSIVE LOCKS, ACCESS EXCLUSIVE LOCKS Andrew Dunstan
• SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. aditya desai
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Bharath Rupireddy
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Pavel Stehule
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Justin Pryzby
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. aditya desai
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Bruce Momjian
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. aditya desai
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Bruce Momjian
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Tom Lane
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Justin Pryzby
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Bruce Momjian
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. aditya desai
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. aditya desai
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Pavel Stehule
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. aditya desai
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Pavel Stehule
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. aditya desai
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Bruce Momjian
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. aditya desai
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Michael Lewis
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. aditya desai
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Bruce Momjian
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. aditya desai
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Pavel Stehule
  • Re: SELECT Query taking 200 ms on PostgreSQL compared to 4 ms on Oracle after migration. Bruce Momjian
• High-volume writes - what is the max throughput possible Geervan Hayatnagarkar
  • Re: High-volume writes - what is the max throughput possible Frits Jalvingh
  • Re: High-volume writes - what is the max throughput possible Hannu Krosing
• Odd (slow) plan choice with min/max Paul McGarry
  • Re: Odd (slow) plan choice with min/max Justin Pryzby
  • Re: Odd (slow) plan choice with min/max Paul McGarry
  • Re: Odd (slow) plan choice with min/max Rick Otten
  • Re: Odd (slow) plan choice with min/max Paul McGarry
  • Re: Odd (slow) plan choice with min/max Yoan SULTAN
• SQL performance issue (postgresql chooses a bad plan when a better one is available) Chris Stephens
  • Re: SQL performance issue (postgresql chooses a bad plan when a better one is available) Laurenz Albe
  • Re: SQL performance issue (postgresql chooses a bad plan when a better one is available) Chris Stephens
  • Re: SQL performance issue (postgresql chooses a bad plan when a better one is available) Hannu Krosing
  • Re: SQL performance issue (postgresql chooses a bad plan when a better one is available) Chris Stephens
  • Re: SQL performance issue (postgresql chooses a bad plan when a better one is available) Hannu Krosing
• Extremely inefficient merge-join Marcin Gozdalik
  • Re: Extremely inefficient merge-join Tom Lane
  • Re: Extremely inefficient merge-join Marcin Gozdalik
• wide table, many many partitions, poor query performance S Bob
  • Re: wide table, many many partitions, poor query performance Justin Pryzby
  • Re: wide table, many many partitions, poor query performance Laurenz Albe
• Users grants with setting options Nagaraj Raj
  • Re: Users grants with setting options David G. Johnston
  • Re: Users grants with setting options Nagaraj Raj
• Fwd: different execution time for the same query (and same DB status) Francesco De Angelis
  • RE: different execution time for the same query (and same DB status) Michel SALAIS
  • Re: different execution time for the same query (and same DB status) Julien Rouhaud
  • Re: different execution time for the same query (and same DB status) Tom Lane
  • Re: different execution time for the same query (and same DB status) Michael Lewis
  • Re: different execution time for the same query (and same DB status) Francesco De Angelis
  • Re: Fwd: different execution time for the same query (and same DB status) Justin Pryzby
  • Re: Fwd: different execution time for the same query (and same DB status) Francesco De Angelis
  • Re: Fwd: different execution time for the same query (and same DB status) Michael Lewis
  • Re: Fwd: different execution time for the same query (and same DB status) Francesco De Angelis
  • How do we hint a query to use index in postgre Manish Lad
  • Re: How do we hint a query to use index in postgre Gaetano Mendola
  • Re: How do we hint a query to use index in postgre Manish Lad
  • Re: How do we hint a query to use index in postgre Nikhil Shetty
• Slow query performance inside a transaction on a clean database val.janeiko
  • Re: Slow query performance inside a transaction on a clean database Laurenz Albe
• tables meta data collection Nagaraj Raj
  • Re: tables meta data collection Justin Pryzby
• High availability management tool. Rodriguez Pablo A
  • Re: High availability management tool. Dorian Hoxha
  • Re: High availability management tool. Hüseyin Demir
  • Re: High availability management tool. Adalberto Caccia
• Performance issues related to left join and order by Liu, Xinyu
  • Re: Performance issues related to left join and order by David Rowley
• Potential performance issues related to group by and covering index Liu, Xinyu
  • Re: Potential performance issues related to group by and covering index Pavel Stehule
  • Re: Potential performance issues related to group by and covering index David Rowley
  • Re: Potential performance issues related to group by and covering index Michael Lewis
  • Re: Potential performance issues related to group by and covering index David Rowley
  • Re: Potential performance issues related to group by and covering index Hannu Krosing
• Potential performance issues Jung, Jinho
  • Re: Potential performance issues Andrew Dunstan
  • Re: Potential performance issues MichaelDBA
  • Re: Potential performance issues Bob Jolliffe
  • Re: Potential performance issues Rick Otten
  • Re: Potential performance issues MichaelDBA
  • Re: Potential performance issues Jung, Jinho
  • Re: Potential performance issues Pavel Stehule
  • Re: Potential performance issues Hannu Krosing
  • Re: Potential performance issues Thomas Kellerer
• Re: Disabling options lowers the estimated cost of a query Tom Lane
  • Re: Disabling options lowers the estimated cost of a query Arne Roland
  • Re: Disabling options lowers the estimated cost of a query Tomas Vondra
  • Re: Disabling options lowers the estimated cost of a query Tom Lane
  • Re: Disabling options lowers the estimated cost of a query Tom Lane
  • Re: Disabling options lowers the estimated cost of a query Tomas Vondra
• Postgres performance comparing GCP and AWS Maurici Meneghetti
  • Re: Postgres performance comparing GCP and AWS Gunther Schadow
  • Re: Postgres performance comparing GCP and AWS Milos Babic
  • Re: Postgres performance comparing GCP and AWS Julien Rouhaud
  • Re: Postgres performance comparing GCP and AWS Igor Gois
  • Re: Postgres performance comparing GCP and AWS Philip Semanchuk
  • Re: Postgres performance comparing GCP and AWS Igor Gois
  • Re: Postgres performance comparing GCP and AWS Philip Semanchuk
  • Re: Postgres performance comparing GCP and AWS Igor Gois
  • Re: Postgres performance comparing GCP and AWS Philip Semanchuk
  • Re: Postgres performance comparing GCP and AWS Justin Pitts
  • Re: Postgres performance comparing GCP and AWS Hannu Krosing
  • Re: Postgres performance comparing GCP and AWS Imre Samu
• FreeBSD UFS & fsync Luca Ferrari
  • Re: FreeBSD UFS & fsync Thomas Munro
  • Re: FreeBSD UFS & fsync Luca Ferrari
  • Re: FreeBSD UFS & fsync Luca Ferrari
  • Re: FreeBSD UFS & fsync Bruce Momjian
  • Re: FreeBSD UFS & fsync Luca Ferrari
  • Re: FreeBSD UFS & fsync Thomas Munro
  • Re: FreeBSD UFS & fsync Bruce Momjian
  • Re: FreeBSD UFS & fsync Luca Ferrari
• Slow query and wrong row estimates for CTE Dane Foster
  • Re: Slow query and wrong row estimates for CTE Justin Pryzby
  • Re: Slow query and wrong row estimates for CTE Dane Foster
  • Re: Slow query and wrong row estimates for CTE Michael Lewis
  • Re: Slow query and wrong row estimates for CTE Dane Foster
  • Re: Slow query and wrong row estimates for CTE Dane Foster
  • Re: Slow query and wrong row estimates for CTE Dane Foster
  • Re: Slow query and wrong row estimates for CTE Yoan SULTAN
  • Re: Slow query and wrong row estimates for CTE Dane Foster
  • Re: Slow query and wrong row estimates for CTE Yoan SULTAN
• Understanding logical replication lag Patrick Molgaard
• RE: Need information on how MM frees up disk space (vaccum) after scheduled DB cleanup by BGwCronScript/BGwLogCleaner M Tarkeshwar Rao
• How to deal with analyze gathering irrelevant stats Rémi Chatenay
  • Re: How to deal with analyze gathering irrelevant stats Justin Pryzby
  • Re: How to deal with analyze gathering irrelevant stats Adam Brusselback
  • Re: How to deal with analyze gathering irrelevant stats Michael Lewis
  • Re: How to deal with analyze gathering irrelevant stats Rémi Chatenay
  • Re: How to deal with analyze gathering irrelevant stats Michael Lewis
• High COMMIT times Don Seiler
  • Re: High COMMIT times Joshua Drake
  • Re: High COMMIT times Don Seiler
  • Re: High COMMIT times Joshua Drake
  • Re: High COMMIT times Kenneth Marshall
  • Re: High COMMIT times Don Seiler
  • Re: High COMMIT times Laurenz Albe
  • Re: High COMMIT times Craig Jackson
  • Re: High COMMIT times Don Seiler
  • Re: High COMMIT times José Arthur Benetasso Villanova
  • Re: High COMMIT times Don Seiler
  • Re: High COMMIT times Laurenz Albe
  • Re: High COMMIT times Craig Jackson
  • Re: High COMMIT times Jeff Janes
  • Re: High COMMIT times Don Seiler
  • Re: High COMMIT times Craig Jackson
  • Re: High COMMIT times Don Seiler
  • Re: High COMMIT times Don Seiler
• Slow recursive CTE query questions, with row estimate and n_distinct issues Christopher Baines
  • Re: Slow recursive CTE query questions, with row estimate and n_distinct issues Michael Lewis
  • Re: Slow recursive CTE query questions, with row estimate and n_distinct issues Christopher Baines
  • Re: Slow recursive CTE query questions, with row estimate and n_distinct issues Greg Spiegelberg
  • Re: Slow recursive CTE query questions, with row estimate and n_distinct issues Christopher Baines
• Conundrum with scaling out of bottleneck with hot standby, PgPool-II, etc. Gunther Schadow
  • Re: Conundrum with scaling out of bottleneck with hot standby, PgPool-II, etc. Marco Colli
  • Re: Conundrum with scaling out of bottleneck with hot standby, PgPool-II, etc. Bruce Momjian
• Reversing NULLS in ORDER causes index not to be used? Ken Tanzer

• Earlier messages
• Later messages