pgsql-performance  

Messages by Thread

• About Query Performaces Problem Hüseyin Ellezer
  • Re: About Query Performaces Problem Pavel Stehule
  • Re: About Query Performaces Problem Hüseyin Ellezer
  • Re: About Query Performaces Problem Pavel Stehule
  • Re: About Query Performaces Problem Julien Rouhaud
• Same query 10000x More Time Avi Weinberg
  • Re: Same query 10000x More Time Vijaykumar Jain
  • Re: Same query 10000x More Time Kyotaro Horiguchi
  • RE: Same query 10000x More Time Avi Weinberg
  • Re: Same query 10000x More Time Vijaykumar Jain
  • RE: Same query 10000x More Time Avi Weinberg
  • Re: Same query 10000x More Time Vijaykumar Jain
• VACUUM: Nonremovable rows due to wal sender process Steve Nixon
  • Re:VACUUM: Nonremovable rows due to wal sender process Sergei Kornilov
  • Re: VACUUM: Nonremovable rows due to wal sender process Steve Nixon
• 9.6 write time Marc Millas
  • Re: 9.6 write time Tom Lane
  • Re: 9.6 write time Marc Millas
  • Re: 9.6 write time Tom Lane
  • Re: 9.6 write time Marc Millas
• WAL files keep piling up Zbigniew Kostrzewa
  • Re: WAL files keep piling up Ninad Shah
  • Re: WAL files keep piling up Zbigniew Kostrzewa
  • Re: WAL files keep piling up Tom Lane
  • Re: WAL files keep piling up Zbigniew Kostrzewa
  • Re: WAL files keep piling up Laurenz Albe
  • Re: WAL files keep piling up Zbigniew Kostrzewa
• Query is slower with a large proportion of NULLs in several columns Lars Bergeson
  • Re: Query is slower with a large proportion of NULLs in several columns David G. Johnston
  • Re: Query is slower with a large proportion of NULLs in several columns Tom Lane
  • Re: Query is slower with a large proportion of NULLs in several columns Lars Bergeson
  • Re: Query is slower with a large proportion of NULLs in several columns Justin Pryzby
  • Re: Query is slower with a large proportion of NULLs in several columns Tom Lane
  • Re: Query is slower with a large proportion of NULLs in several columns David G. Johnston
  • Re: Query is slower with a large proportion of NULLs in several columns Tom Lane
  • Re: Query is slower with a large proportion of NULLs in several columns Justin Pryzby
  • Re: Query is slower with a large proportion of NULLs in several columns Lars Bergeson
  • Re: Query is slower with a large proportion of NULLs in several columns Tom Lane
  • Re: Query is slower with a large proportion of NULLs in several columns David G. Johnston
  • Re: Query is slower with a large proportion of NULLs in several columns David G. Johnston
• PostgreSQLv14 performance client-server-HammerDB arjun shetty
• pg_trgm word_similarity query does not use index for input strings longer than 8 characters pgsql-performance
  • Re: pg_trgm word_similarity query does not use index for input strings longer than 8 characters Laurenz Albe
  • Re: pg_trgm word_similarity query does not use index for input strings longer than 8 characters Tom Lane
  • Re: pg_trgm word_similarity query does not use index for input strings longer than 8 characters pgsql-performance
• An I/O error occurred while sending to the backend (PG 13.4) [email protected]
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Justin Pryzby
  • RE: An I/O error occurred while sending to the backend (PG 13.4) [email protected]
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Justin Pryzby
  • RE: An I/O error occurred while sending to the backend (PG 13.4) [email protected]
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Justin Pryzby
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Justin Pryzby
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Justin Pryzby
  • RE: An I/O error occurred while sending to the backend (PG 13.4) [email protected]
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Justin Pryzby
  • RE: An I/O error occurred while sending to the backend (PG 13.4) [email protected]
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Justin Pryzby
  • RE: An I/O error occurred while sending to the backend (PG 13.4) [email protected]
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Ranier Vilela
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Justin Pryzby
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Ranier Vilela
  • RE: An I/O error occurred while sending to the backend (PG 13.4) [email protected]
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Ranier Vilela
  • RE: An I/O error occurred while sending to the backend (PG 13.4) [email protected]
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Justin Pryzby
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Ranier Vilela
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Justin Pryzby
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Ranier Vilela
  • RE: An I/O error occurred while sending to the backend (PG 13.4) [email protected]
  • Re: An I/O error occurred while sending to the backend (PG 13.4) Ranier Vilela
• LwLockRelease performance Ashkil Dighin
  • Re: LwLockRelease performance Tom Lane
  • Re: LwLockRelease performance Andres Freund
• pg_dump backup verification Daulat
  • AW: [External] pg_dump backup verification Dirk Krautschick
  • Re: pg_dump backup verification Justin Pryzby
• Postgres process count GCC vs Clang is Different on autovaccum=on hpc researcher_mspk
  • Re: Postgres process count GCC vs Clang is Different on autovaccum=on Tomas Vondra
• Out of memory error aditya desai
  • Re: Out of memory error Tom Lane
  • Re: Out of memory error aditya desai
  • Re: Out of memory error Thomas Kellerer
  • Re: Out of memory error aditya desai
  • Re: Out of memory error Michael Lewis
  • Re: Out of memory error aditya desai
  • Re: Out of memory error Thomas Kellerer
  • Re: Out of memory error aditya desai
  • Re: Out of memory error Thomas Kellerer
  • Re: Out of memory error aditya desai
• Re: Need help identifying a periodic performance issue. Justin Pryzby
  • Re: Need help identifying a periodic performance issue. Robert Creager
  • Re: Need help identifying a periodic performance issue. Thomas Munro
  • Re: Need help identifying a periodic performance issue. Robert Creager
  • Re: Need help identifying a periodic performance issue. Thomas Munro
  • Re: Need help identifying a periodic performance issue. Thomas Munro
  • Re: Need help identifying a periodic performance issue. Robert Creager
  • Re: Need help identifying a periodic performance issue. Justin Pryzby
  • Re: Need help identifying a periodic performance issue. Tom Lane
  • Re: Need help identifying a periodic performance issue. Thomas Munro
  • Re: Need help identifying a periodic performance issue. Justin Pryzby
  • Re: Need help identifying a periodic performance issue. Robert Creager
  • Re: Need help identifying a periodic performance issue. Thomas Munro
  • Re: Need help identifying a periodic performance issue. Justin Pryzby
  • Re: Need help identifying a periodic performance issue. Robert Creager
  • Re: Need help identifying a periodic performance issue. Thomas Munro
  • Re: Need help identifying a periodic performance issue. Tom Lane
  • Re: Need help identifying a periodic performance issue. Robert Creager
  • Re: Need help identifying a periodic performance issue. Robert Creager
  • Re: Need help identifying a periodic performance issue. Robert Creager
  • Re: Need help identifying a periodic performance issue. Robert Creager
  • Re: Need help identifying a periodic performance issue. Justin Pryzby
  • Re: Need help identifying a periodic performance issue. Robert Creager
  • Re: Need help identifying a periodic performance issue. Robert Creager
  • Re: Need help identifying a periodic performance issue. Robert Creager
• postgresql13-llvm jit-13.5-1PGDG.rhel8.x86_64 Mladen Gogala
  • Re: postgresql13-llvm jit-13.5-1PGDG.rhel8.x86_64 Pavel Stehule
  • Re: postgresql13-llvm jit-13.5-1PGDG.rhel8.x86_64 Mladen Gogala
  • Re: postgresql13-llvm jit-13.5-1PGDG.rhel8.x86_64 Rick Otten
• performance of analytical query Jiří Fejfar
  • Re: performance of analytical query Justin Pryzby
  • Re: performance of analytical query Michael Lewis
  • Re: performance of analytical query Justin Pryzby
  • Re: performance of analytical query Jiří Fejfar
  • Re: performance of analytical query Justin Pryzby
• EXISTS by itself vs SELECT EXISTS much slower in query. Jimmy A
  • Re: EXISTS by itself vs SELECT EXISTS much slower in query. Vasya Boytsov
  • Re: EXISTS by itself vs SELECT EXISTS much slower in query. Tom Lane
  • Re: EXISTS by itself vs SELECT EXISTS much slower in query. Jimmy A
• JIT llvm11 package ANASTACIO Tiago
• PostgreSQLv14 TPC-H performance GCC vs Clang arjun shetty
  • Re: PostgreSQLv14 TPC-H performance GCC vs Clang Imre Samu
  • Re: PostgreSQLv14 TPC-H performance GCC vs Clang arjun shetty
  • Re: PostgreSQLv14 TPC-H performance GCC vs Clang Tomas Vondra
  • PostgreSQLv14 TPC-H performance GCC vs Clang arjun shetty
  • Re: PostgreSQLv14 TPC-H performance GCC vs Clang Imre Samu
  • Re: PostgreSQLv14 TPC-H performance GCC vs Clang arjun shetty
• Views don't seem to use indexes? Tim Slechta
  • Re: Views don't seem to use indexes? David G. Johnston
  • Re: Views don't seem to use indexes? Tom Lane
  • Re: Views don't seem to use indexes? Tim Slechta
• Postgres views cannot use both union and join/where Mithran Kulasekaran
  • Re: Postgres views cannot use both union and join/where David G. Johnston
  • Re: Postgres views cannot use both union and join/where Benedict Holland
  • Re: Postgres views cannot use both union and join/where Michael Lewis
  • Re: Postgres views cannot use both union and join/where David G. Johnston
  • Re: Postgres views cannot use both union and join/where Tom Lane
  • Re: Postgres views cannot use both union and join/where David G. Johnston
• Fwd: Query out of memory aditya desai
  • Re: Query out of memory Adam Brusselback
  • Re: Query out of memory Dave Cramer
  • Re: Fwd: Query out of memory Justin Pryzby
  • Re: Query out of memory aditya desai
  • Re: Query out of memory Michael Lewis
  • Re: Query out of memory aditya desai
  • Re: Query out of memory Ninad Shah
  • Sv: Fwd: Query out of memory Andreas Joseph Krogh
• Lock contention high Ashkil Dighin
  • Re: Lock contention high Mikhail Zhilin
  • Re: Lock contention high Ashkil Dighin
  • Re: Lock contention high Mikhail Zhilin
  • Re: Lock contention high Laurenz Albe
  • Re: Lock contention high Ashkil Dighin
  • Re: Lock contention high Laurenz Albe
  • Re: Lock contention high Mladen Gogala
  • Re: Lock contention high Justin Pryzby
  • Re: Lock contention high MichaelDBA
  • Re: Lock contention high Paul Friedman
  • Re: Lock contention high Ashkil Dighin
  • Re: Lock contention high Peter Geoghegan
  • Re: Lock contention high Ashkil Dighin
  • Re: Lock contention high Jeremy Schneider
  • Re: Lock contention high Peter Geoghegan
  • Re: Lock contention high Andres Freund
  • Re: Lock contention high Michael Lewis
  • Re: Lock contention high Andres Freund
  • Re: Lock contention high Ashkil Dighin
  • Re: Lock contention high Andres Freund
  • Re: Lock contention high Ashkil Dighin
  • Re: Lock contention high Tom Lane
  • Re: Lock contention high arjun shetty
  • Re: Lock contention high arjun shetty
  • Re: Lock contention high Yura Sokolov
• PG 12 slow selects from pg_settings Julius Tuskenis
  • Re: PG 12 slow selects from pg_settings Ranier Vilela
  • Re: PG 12 slow selects from pg_settings Julius Tuskenis
  • Re: PG 12 slow selects from pg_settings Ranier Vilela
  • Re: PG 12 slow selects from pg_settings Julius Tuskenis
• Troubleshooting a long running delete statement Dirschel, Steve
  • Re: Troubleshooting a long running delete statement Mladen Gogala
  • RE: [EXT] Re: Troubleshooting a long running delete statement Dirschel, Steve
  • Re: [EXT] Re: Troubleshooting a long running delete statement Mladen Gogala
  • Re: Troubleshooting a long running delete statement Justin Pryzby
  • RE: [EXT] Re: Troubleshooting a long running delete statement Dirschel, Steve
  • Re: [EXT] Re: Troubleshooting a long running delete statement Mladen Gogala
  • Re: [EXT] Re: Troubleshooting a long running delete statement Maciek Sakrejda
  • Re: [EXT] Re: Troubleshooting a long running delete statement Corey Huinker
  • Re: Troubleshooting a long running delete statement Laurenz Albe
  • Re: Troubleshooting a long running delete statement Michael Lewis
• Better, consistent instrumentation for postgreSQL using a similar API as Oracle Jeff Holt
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Laurenz Albe

• Earlier messages
• Later messages