pgsql-performance  

Messages by Thread

• • Re: [PERFORM] Queries intermittently slow Scott Rankin
  • Re: [PERFORM] Queries intermittently slow Jim Nasby
  • Re: [PERFORM] Queries intermittently slow Scott Rankin
  • Re: [PERFORM] Queries intermittently slow Tom Lane
  • Re: [PERFORM] Queries intermittently slow Scott Rankin
  • Re: [PERFORM] Queries intermittently slow Tom Lane
  • Re: [PERFORM] Queries intermittently slow Andres Freund
  • Re: [PERFORM] Queries intermittently slow Jim Nasby
• [PERFORM] Materialized view performance problems Tom McLoughlin
  • Re: [PERFORM] Materialized view performance problems Andreas Kretschmer
  • Re: [PERFORM] Materialized view performance problems Tom McLoughlin
  • Re: [PERFORM] Materialized view performance problems Andreas Kretschmer
• [PERFORM] Proposal for unlogged tables Mark Zealey
  • Re: [PERFORM] Proposal for unlogged tables Yves Dorfsman
  • Re: [PERFORM] Proposal for unlogged tables Mark Zealey
  • Re: [PERFORM] Proposal for unlogged tables Andres Freund
  • Re: [PERFORM] Proposal for unlogged tables Mark Zealey
  • Re: [PERFORM] Proposal for unlogged tables Andres Freund
• [PERFORM] Plan differences Anton Melser
  • Re: [PERFORM] Plan differences Pavel Stehule
  • Re: [PERFORM] Plan differences Anton Melser
  • Re: [PERFORM] Plan differences Tom Lane
  • Re: [PERFORM] Plan differences Jim Nasby
  • Re: [PERFORM] Plan differences Tom Lane
  • Re: [PERFORM] Plan differences Anton Melser
  • Re: [PERFORM] Plan differences Anton Melser
  • Re: [PERFORM] Plan differences Adam Pearson
  • Re: [PERFORM] Plan differences Anton Melser
• [PERFORM] Connections "Startup" Artem Tomyuk
  • Re: [PERFORM] Connections "Startup" Pavel Stehule
  • Re: [PERFORM] Connections "Startup" Rick Otten
  • Re: [PERFORM] Connections "Startup" Jim Nasby
  • Re: [ADMIN] [PERFORM] Connections "Startup" Om Prakash Jaiswal
  • Re: [ADMIN] [PERFORM] Connections "Startup" Pavel Stehule
• [PERFORM] Terrible plan choice for view with distinct on clause Adam Brusselback
  • Re: [PERFORM] Terrible plan choice for view with distinct on clause Tom Lane
  • Re: [PERFORM] Terrible plan choice for view with distinct on clause Adam Brusselback
  • Re: [PERFORM] Terrible plan choice for view with distinct on clause Adam Brusselback
• [PERFORM] Selectivity for lopsided foreign key columns Mikkel Lauritsen
  • Re: [PERFORM] Selectivity for lopsided foreign key columns Tom Lane
  • Re: [PERFORM] Selectivity for lopsided foreign key columns Mikkel Lauritsen
• [PERFORM] Can't explain db size Matteo Grolla
  • Re: [PERFORM] Can't explain db size Andreas Kretschmer
  • Re: [PERFORM] Can't explain db size Matteo Grolla
  • Re: [PERFORM] Can't explain db size Matteo Grolla
  • Re: [PERFORM] Can't explain db size Matteo Grolla
  • Re: [PERFORM] Can't explain db size Jim Nasby
• [PERFORM] Getting an optimal plan on the first execution of a pl/pgsql function Pedro França
  • Re: [PERFORM] Getting an optimal plan on the first execution of a pl/pgsql function David G. Johnston
  • Re: [PERFORM] Getting an optimal plan on the first execution of a pl/pgsql function Tom Lane
  • Re: [PERFORM] Getting an optimal plan on the first execution of a pl/pgsql function Pedro França
• [PERFORM] Performance difference between Slon master and slave Matthew Lunnon
  • Re: [PERFORM] Performance difference between Slon master and slave Jim Nasby
  • Re: [PERFORM] Performance difference between Slon master and slave Mattthew Lunnon
• [PERFORM] partitioned table set and indexes Rick Otten
  • Re: [PERFORM] partitioned table set and indexes Andreas Kretschmer
  • Re: [PERFORM] partitioned table set and indexes Rick Otten
  • Re: [PERFORM] partitioned table set and indexes Andreas Kretschmer
  • Re: [PERFORM] partitioned table set and indexes Rick Otten
  • Re: [PERFORM] partitioned table set and indexes Andreas Kretschmer
  • Re: [PERFORM] partitioned table set and indexes Rick Otten
  • Re: [PERFORM] partitioned table set and indexes Andreas Kretschmer
  • Re: [PERFORM] partitioned table set and indexes Kevin Grittner
• [PERFORM] Estimation row error Mathieu VINCENT
  • Re: [PERFORM] Estimation row error Mathieu VINCENT
  • Re: [PERFORM] Estimation row error Mathieu VINCENT
  • Re: [PERFORM] Estimation row error Gunnar "Nick" Bluth
  • Re: [PERFORM] Estimation row error Andreas Kretschmer
  • Re: [PERFORM] Estimation row error Gunnar "Nick" Bluth
  • Re: [PERFORM] Estimation row error Mathieu VINCENT
  • Re: [PERFORM] Estimation row error Matteo Grolla
  • Re: [PERFORM] Estimation row error Mathieu VINCENT
  • Re: [PERFORM] Estimation row error Mathieu VINCENT
  • Re: [PERFORM] Estimation row error Mathieu VINCENT
  • Re: [PERFORM] Estimation row error Pavel Stehule
• [PERFORM] Advise needed for a join query with a where conditional ankur_adwyze
  • Re: [PERFORM] Advise needed for a join query with a where conditional ankur_adwyze
  • Re: [PERFORM] Advise needed for a join query with a where conditional Jim Nasby
  • Re: [PERFORM] Advise needed for a join query with a where conditional Jeff Janes
• [PERFORM] postgresql upgrade from 9.3 to 9.4 error Sheena, Prabhjot
• [PERFORM] checkpoints, proper config Tory M Blue
  • Re: [PERFORM] checkpoints, proper config Joshua D. Drake
  • Re: [PERFORM] checkpoints, proper config Tory M Blue
  • Re: [PERFORM] checkpoints, proper config Joshua D. Drake
  • Re: [PERFORM] checkpoints, proper config Tory M Blue
  • Re: [PERFORM] checkpoints, proper config Joshua D. Drake
  • Re: [PERFORM] checkpoints, proper config Jim Nasby
  • Re: [PERFORM] checkpoints, proper config Tomas Vondra
  • Re: [PERFORM] checkpoints, proper config Alvaro Herrera
  • Re: [PERFORM] checkpoints, proper config Tomas Vondra
  • Re: [PERFORM] checkpoints, proper config Jim Nasby
• [PERFORM] Slow Index Creation, why is it not consuming more memory. Tory M Blue
  • Re: [PERFORM] Slow Index Creation, why is it not consuming more memory. Peter Geoghegan
• [PERFORM] ossp-uuid: Performance considerations for different UUID approaches? Brendan McCollam
• [PERFORM] Index scan cost calculation Glyn Astill
  • Re: [PERFORM] Index scan cost calculation Glyn Astill
  • Re: [PERFORM] Index scan cost calculation Tom Lane
  • Re: [PERFORM] Index scan cost calculation Glyn Astill
  • Re: [PERFORM] Index scan cost calculation Tom Lane
  • Re: [PERFORM] Index scan cost calculation Jeff Janes
  • Re: [PERFORM] Index scan cost calculation Glyn Astill
  • Re: [PERFORM] Index scan cost calculation Jeff Janes
  • Re: [PERFORM] Index scan cost calculation Glyn Astill
  • Re: [PERFORM] Index scan cost calculation Jim Nasby
  • Re: [PERFORM] Index scan cost calculation Glyn Astill
• [PERFORM] No index only scan on md5 index Adam Brusselback
  • Re: [PERFORM] No index only scan on md5 index David G. Johnston
  • Re: [PERFORM] No index only scan on md5 index Adam Brusselback
  • Re: [PERFORM] No index only scan on md5 index Tom Lane
  • Re: [PERFORM] No index only scan on md5 index Adam Brusselback
  • Re: [PERFORM] No index only scan on md5 index Albe Laurenz
• [PERFORM] Query that took a lot of time in Postgresql when not using trim in order by Blas Pico
  • Re: [PERFORM] Query that took a lot of time in Postgresql when not using trim in order by Alex Ignatov
  • Re: [PERFORM] Query that took a lot of time in Postgresql when not using trim in order by Evgeniy Shishkin
  • Re: [PERFORM] Query that took a lot of time in Postgresql when not using trim in order by Blas Pico
  • Re: [PERFORM] Query that took a lot of time in Postgresql when not using trim in order by Peter J. Holzer
  • Re: [PERFORM] Query that took a lot of time in Postgresql when not using trim in order by Tom Lane
• [PERFORM] Why is now()::date so much faster than current_date Thomas Kellerer
  • Re: [PERFORM] Why is now()::date so much faster than current_date David Rowley
  • Re: [PERFORM] Why is now()::date so much faster than current_date Tom Lane
• [PERFORM] Simple delete query is taking too long (never ends) Massalin Yerzhan
  • Re: [PERFORM] Simple delete query is taking too long (never ends) Tom Lane
  • Re: [PERFORM] Simple delete query is taking too long (never ends) Merlin Moncure
  • Re: [PERFORM] Simple delete query is taking too long (never ends) Tom Lane
  • Re: [PERFORM] Simple delete query is taking too long (never ends) Craig James
  • Re: [PERFORM] Simple delete query is taking too long (never ends) Merlin Moncure
  • Re: [PERFORM] Simple delete query is taking too long (never ends) Tom Lane
  • Re: [PERFORM] Simple delete query is taking too long (never ends) Merlin Moncure
  • Re: [PERFORM] Simple delete query is taking too long (never ends) Scott Marlowe
• [PERFORM] Queries getting canceled inside a proc that seems to slow down randomly Skarsol
  • Re: [PERFORM] Queries getting canceled inside a proc that seems to slow down randomly Jim Nasby
  • Re: [PERFORM] Queries getting canceled inside a proc that seems to slow down randomly Skarsol
  • Re: [PERFORM] Queries getting canceled inside a proc that seems to slow down randomly Jim Nasby
  • Re: [PERFORM] Queries getting canceled inside a proc that seems to slow down randomly Skarsol
• [PERFORM] Hanging query on a fresh restart Jason Jho
  • Re: [PERFORM] Hanging query on a fresh restart Jim Nasby
  • Re: [PERFORM] Hanging query on a fresh restart Kevin Grittner
• [PERFORM] Slow 3 Table Join with v bad row estimate David Osborne
  • Re: [PERFORM] Slow 3 Table Join with v bad row estimate Tom Lane
  • Re: [PERFORM] Slow 3 Table Join with v bad row estimate David Osborne
  • Re: [PERFORM] Slow 3 Table Join with v bad row estimate Tom Lane
  • Re: [PERFORM] Slow 3 Table Join with v bad row estimate David Osborne
  • Re: [PERFORM] Slow 3 Table Join with v bad row estimate Igor Neyman
  • Re: [PERFORM] Slow 3 Table Join with v bad row estimate David Osborne
• [PERFORM] querying jsonb for arrays inside a hash Joe Van Dyk
  • Re: [PERFORM] querying jsonb for arrays inside a hash Tom Lane
  • Re: [PERFORM] querying jsonb for arrays inside a hash Joe Van Dyk
• [PERFORM] HASH Artem Tomyuk
  • Re: [PERFORM] HASH Jeff Janes
• [PERFORM] PostgreSQL limitation FattahRozzaq
  • Re: [PERFORM] PostgreSQL limitation Michael Paquier
• [PERFORM] Slow query in trigger function Guido Niewerth
  • Re: [PERFORM] Slow query in trigger function Tom Lane
  • Re: [PERFORM] Slow query in trigger function Guido Niewerth
  • Re: [PERFORM] Slow query in trigger function Tom Lane
  • Re: [PERFORM] Slow query in trigger function Guido Niewerth
• [PERFORM] GIN index always doing Re-check condition, postgres 9.1 Andrey Osenenko
  • Re: [PERFORM] GIN index always doing Re-check condition, postgres 9.1 Jeff Janes
  • Re: [PERFORM] GIN index always doing Re-check condition, postgres 9.1 Andrey Osenenko
  • Re: [PERFORM] GIN index always doing Re-check condition, postgres 9.1 Jim Nasby
  • Re: [PERFORM] GIN index always doing Re-check condition, postgres 9.1 Jeff Janes
  • Re: [PERFORM] GIN index always doing Re-check condition, postgres 9.1 Andrey Osenenko
• [PERFORM] Query optimizer plans with very small selectivity estimates Matthew Bellew
  • Re: [PERFORM] Query optimizer plans with very small selectivity estimates Tom Lane
  • Re: [PERFORM] Query optimizer plans with very small selectivity estimates Josh Berkus
• [PERFORM] Scalability to more than 64 cores With PG 9.4 and RHEL 7.1 Kernel 3.10 Javier Muro
  • Re: [PERFORM] Scalability to more than 64 cores With PG 9.4 and RHEL 7.1 Kernel 3.10 Alex Ignatov
• [PERFORM] Partition Constraint Exclusion Limits GMail
  • Re: [PERFORM] Partition Constraint Exclusion Limits David G. Johnston
  • Re: [PERFORM] Partition Constraint Exclusion Limits Vitalii Tymchyshyn
  • Re: [PERFORM] Partition Constraint Exclusion Limits Jim Nasby
• [PERFORM] Query planner wants to use seq scan Bertrand Paquet
  • Re: [PERFORM] Query planner wants to use seq scan Alex Ignatov
  • Re: [PERFORM] Query planner wants to use seq scan Bertrand Paquet
  • Re: [PERFORM] Query planner wants to use seq scan Alex Ignatov
  • Re: [PERFORM] Query planner wants to use seq scan Bertrand Paquet
  • Re: [PERFORM] Query planner wants to use seq scan Alex Ignatov
  • Re: [PERFORM] Query planner wants to use seq scan Bertrand Paquet
  • Re: [PERFORM] Query planner wants to use seq scan Tom Lane
  • Re: [PERFORM] Query planner wants to use seq scan Bertrand Paquet
  • Re: [PERFORM] Query planner wants to use seq scan Bertrand Paquet
  • Re: [PERFORM] Query planner wants to use seq scan Bertrand Paquet
  • Re: [PERFORM] Query planner wants to use seq scan Jim Nasby
  • Re: [PERFORM] Query planner wants to use seq scan Alex Ignatov
  • Re: [PERFORM] Query planner wants to use seq scan Bertrand Paquet
• [PERFORM] GroupAggregate and Integer Arrays David Osborne
  • Re: [PERFORM] GroupAggregate and Integer Arrays Jeff Janes
  • Re: [PERFORM] GroupAggregate and Integer Arrays David Osborne
  • Re: [PERFORM] GroupAggregate and Integer Arrays Jeff Janes
  • Re: [PERFORM] GroupAggregate and Integer Arrays Marc Mamin
  • Re: [PERFORM] GroupAggregate and Integer Arrays Merlin Moncure
  • Re: [PERFORM] GroupAggregate and Integer Arrays David Osborne
  • Re: [PERFORM] GroupAggregate and Integer Arrays Merlin Moncure
• [PERFORM] Recursive query performance issue Jamie Koceniak
  • Re: [PERFORM] Recursive query performance issue Pavel Stehule
  • Re: [PERFORM] Recursive query performance issue Jamie Koceniak
  • Re: [PERFORM] Recursive query performance issue Pavel Stehule
  • Re: [PERFORM] Recursive query performance issue Jamie Koceniak
  • Re: [PERFORM] Recursive query performance issue Jamie Koceniak
  • Re: [PERFORM] Recursive query performance issue Pavel Stehule

• Earlier messages
• Later messages