pgsql-performance  

Messages by Thread

• 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
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Mladen Gogala
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle michael...@sqlexec.com
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Mladen Gogala
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Peter Geoghegan
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Mladen Gogala
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Peter Geoghegan
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Ranier Vilela
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Laurenz Albe
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Mladen Gogala
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Bruce Momjian
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Peter Geoghegan
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Mladen Gogala
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Tim
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Mladen Gogala
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Jeremy Schneider
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Bruce Momjian
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Jeremy Schneider
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Bruce Momjian
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Mladen Gogala
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Bruce Momjian
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Thomas Kellerer
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Bruce Momjian
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Julien Rouhaud
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Thomas Kellerer
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Mladen Gogala
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Franck Pachot
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Laurenz Albe
  • Re: Better, consistent instrumentation for postgreSQL using a similar API as Oracle Bruce Momjian
• Query going to all paritions aditya desai
  • Re: Query going to all paritions Laurenz Albe
  • Re: Query going to all paritions hubert depesz lubaczewski
  • Re: Query going to all paritions aditya desai
• How to improve cockroach performance with pgbench? Fabien COELHO
• Re: Problem with indices from 10 to 13 Ranier Vilela
  • Re: Problem with indices from 10 to 13 Alan Hodgson
  • Re: Problem with indices from 10 to 13 Tom Lane
  • Re: Problem with indices from 10 to 13 Tom Lane
  • Re: Problem with indices from 10 to 13 Justin Pryzby
• Partial index on enum type is not being used, type issue? Kim Johan Andersson
  • Re: Partial index on enum type is not being used, type issue? Tom Lane
• Performance for initial copy when using pg_logical to upgrade Postgres Westwood, Giles
  • Re: Performance for initial copy when using pg_logical to upgrade Postgres Justin Pryzby
  • Re: Performance for initial copy when using pg_logical to upgrade Postgres Westwood, Giles
  • Re: Performance for initial copy when using pg_logical to upgrade Postgres Tim
  • Re: Performance for initial copy when using pg_logical to upgrade Postgres Westwood, Giles
  • Re: Performance for initial copy when using pg_logical to upgrade Postgres Andrew Dunstan
• Re: hashjoins, index loops to retrieve pk/ux constrains in pg12 Michael Lewis
  • Re: hashjoins, index loops to retrieve pk/ux constrains in pg12 Arturas Mazeika
  • Re: hashjoins, index loops to retrieve pk/ux constrains in pg12 Michael Lewis
  • Re: hashjoins, index loops to retrieve pk/ux constrains in pg12 Arturas Mazeika
  • Re: hashjoins, index loops to retrieve pk/ux constrains in pg12 Tom Lane
  • Re: hashjoins, index loops to retrieve pk/ux constrains in pg12 Arturas Mazeika
• multi-tenant queries select wrong index Kirill
  • Re: multi-tenant queries select wrong index Alexey M Boltenkov
• Query executed during pg_dump leads to excessive memory usage Ulf Lohbrügge
  • Re: Query executed during pg_dump leads to excessive memory usage Ranier Vilela
  • Re: Query executed during pg_dump leads to excessive memory usage Ulf Lohbrügge
  • Re: Query executed during pg_dump leads to excessive memory usage Gogala, Mladen
  • Re: Query executed during pg_dump leads to excessive memory usage Tom Lane
• Want function to be called only once in query Steve Pritchard
  • Re: Want function to be called only once in query Jim Mlodgenski
  • Re: Want function to be called only once in query Steve Pritchard
• EnterpriseDB Mladen Gogala
  • Re: EnterpriseDB sbob
  • Re: EnterpriseDB manish yadav
• Postgres chooses slow query plan from time to time Kristjan Mustkivi
  • Re: Postgres chooses slow query plan from time to time Tomas Vondra
  • Re: Postgres chooses slow query plan from time to time Michael Lewis
  • Re: Postgres chooses slow query plan from time to time Justin Pryzby
  • Re: Postgres chooses slow query plan from time to time Kristjan Mustkivi
  • Re: Postgres chooses slow query plan from time to time Laurenz Albe
  • Re: Postgres chooses slow query plan from time to time Jeff Janes
  • Re: Postgres chooses slow query plan from time to time Kristjan Mustkivi
  • Re: Postgres chooses slow query plan from time to time Tom Lane
  • Re: Postgres chooses slow query plan from time to time Kristjan Mustkivi
  • Re: Postgres chooses slow query plan from time to time Tom Lane

• Earlier messages
• Later messages