pgsql-performance  

Messages by Thread

• • Re: Query choosing Bad Index Path (ASC/DESC ordering). Mind Body Nature
• slow "select count(*) from information_schema.tables;" in some cases Lars Aksel Opsahl
  • Re: slow "select count(*) from information_schema.tables;" in some cases Justin Pryzby
  • Re: slow "select count(*) from information_schema.tables;" in some cases Lars Aksel Opsahl
  • Re: slow "select count(*) from information_schema.tables;" in some cases Imre Samu
  • Re: slow "select count(*) from information_schema.tables;" in some cases Vijaykumar Jain
  • Re: slow "select count(*) from information_schema.tables;" in some cases Lars Aksel Opsahl
  • Re: slow "select count(*) from information_schema.tables;" in some cases Tom Lane
  • Re: slow "select count(*) from information_schema.tables;" in some cases Lars Aksel Opsahl
• Terribly slow query with very good plan? Les
  • Re: Terribly slow query with very good plan? Laurenz Albe
  • Re: Terribly slow query with very good plan? Les
  • Re: Terribly slow query with very good plan? Les
  • Re: Terribly slow query with very good plan? Pavel Stehule
  • Re: Terribly slow query with very good plan? Nick Cleaton
  • Re: Terribly slow query with very good plan? Les
  • Re: Terribly slow query with very good plan? Les
  • Re: Terribly slow query with very good plan? Les
  • Re: Terribly slow query with very good plan? Nick Cleaton
  • Re: Terribly slow query with very good plan? Les
  • Re: Terribly slow query with very good plan? Nick Cleaton
  • Re: Terribly slow query with very good plan? Les
  • Re: Terribly slow query with very good plan? Nick Cleaton
  • Re: Terribly slow query with very good plan? Les
  • Re: Terribly slow query with very good plan? Ninad Shah
  • Re: Terribly slow query with very good plan? Nick Cleaton
  • Re: Terribly slow query with very good plan? Les
  • Re: Terribly slow query with very good plan? Nick Cleaton
  • Re: Terribly slow query with very good plan? Les
  • Re: Terribly slow query with very good plan? Thomas Kellerer
  • Re: Terribly slow query with very good plan? Vijaykumar Jain
• Query runs slower as prepared statement - identical execution plans Thomas Kellerer
• PostgreSQL and Linux CPU's Sbob
  • Re: PostgreSQL and Linux CPU's David G. Johnston
• Poor performance PostgreSQL 13/ PostGIS 3.x Lugosi, Jim
  • Re: Poor performance PostgreSQL 13/ PostGIS 3.x Merlin Moncure
• Slow query fixed by replacing equality with a nested query Valentin Janeiko
  • Re: Slow query fixed by replacing equality with a nested query Michael Lewis
  • RE: Slow query fixed by replacing equality with a nested query val.janeiko
  • Re: Slow query fixed by replacing equality with a nested query Valentin Janeiko
  • Re: Slow query fixed by replacing equality with a nested query Michael Lewis
  • Re: Slow query fixed by replacing equality with a nested query Michael Lewis
• PostgreSQL 12.8 Same Query Same Execution Plan Different Time Ludwig Isaac Lim
  • Re: PostgreSQL 12.8 Same Query Same Execution Plan Different Time David G. Johnston
  • RE: PostgreSQL 12.8 Same Query Same Execution Plan Different Time Michel SALAIS
• Unique constraint blues Mladen Gogala
  • Re: Unique constraint blues David G. Johnston
• PGBench connection issue with -C option only T T
• 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

• Earlier messages
• Later messages