pgsql-performance - January 2020

Discussion of PostgreSQL's performance issues. Please see Guide to reporting problems and Slow Query Questions for some tips on how to write your performance question.

Search the Archives

(enter a message-id to go directly to that message)
Advanced Search

Browse Archives

Prev | Next
Jump to day: 2 3 4 6 10 13 14 15 16 17 21 24 26 27 28 30 31

Jan. 3, 2020

Thread Author Time
distinguish index cost component from table component Justin Pryzby 14:14
Re: distinguish index cost component from table component Jeff Janes 14:33
Re: distinguish index cost component from table component 📎 Justin Pryzby 16:03

Jan. 4, 2020

Thread Author Time
allow disabling indexscans without disabling bitmapscans 📎 Justin Pryzby 16:50
Re: allow disabling indexscans without disabling bitmapscans Justin Pryzby 19:34

Jan. 6, 2020

Thread Author Time
doc: alter table references bogus table-specific planner parameters 📎 Justin Pryzby 02:56
Re: doc: alter table references bogus table-specific planner parameters Simon Riggs 03:48
Re: doc: alter table references bogus table-specific planner parameters Justin Pryzby 04:13
Re: doc: alter table references bogus table-specific planner parameters Simon Riggs 04:33

Jan. 10, 2020

Thread Author Time
Bad query plan when you add many OR conditions Marco Colli 01:11
Re: Bad query plan when you add many OR conditions Justin Pryzby 03:06
Re: Bad query plan when you add many OR conditions Marco Colli 11:03
Re: Bad query plan when you add many OR conditions Marco Colli 13:30
Re: Bad query plan when you add many OR conditions Justin Pryzby 13:34
Re: Bad query plan when you add many OR conditions Marco Colli 14:53
Re: Bad query plan when you add many OR conditions Tom Lane 15:18
Re: Bad query plan when you add many OR conditions Marco Colli 16:03
Re: Bad query plan when you add many OR conditions Jeff Janes 17:12

Jan. 13, 2020

Thread Author Time
Seeking reason behind performance gain in 12 with HashAggregate Shira Bezalel 16:29
Re: Seeking reason behind performance gain in 12 with HashAggregate Justin Pryzby 16:42
Re: Seeking reason behind performance gain in 12 with HashAggregate Shira Bezalel 17:34
Re: Seeking reason behind performance gain in 12 with HashAggregate Michael Lewis 18:07
Re: Seeking reason behind performance gain in 12 with HashAggregate Shira Bezalel 20:44
Re: Seeking reason behind performance gain in 12 with HashAggregate Tomas Vondra 21:11
Re: Seeking reason behind performance gain in 12 with HashAggregate Shira Bezalel 21:45
Re: Bad query plan when you add many OR conditions Tomas Vondra 22:14
Re: Seeking reason behind performance gain in 12 with HashAggregate Alvaro Herrera 22:15

Jan. 14, 2020

Thread Author Time
Re: Seeking reason behind performance gain in 12 with HashAggregate Shira Bezalel 00:11
Re: Bad query plan when you add many OR conditions Thomas Kellerer 08:01
shared buffers and startup process Joao Junior 15:29

Jan. 15, 2020

Thread Author Time
Re: shared buffers and startup process Michael Paquier 02:48

Jan. 16, 2020

Thread Author Time
Queries in plpgsql are 6 times slower on partitioned tables Marcin Barczyński 13:21
Bad query plan decision when using multiple column index - postgresql uses only first column then filters Cosmin Prund 14:06
Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Tom Lane 15:11
Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Michael Lewis 16:59
Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Cosmin Prund 17:18
Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Tom Lane 17:27
Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Cosmin Prund 18:15
Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Laurenz Albe 18:20
Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Tom Lane 18:23
Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Michael Lewis 18:52
Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Tom Lane 18:55
Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Cosmin Prund 19:06
Re: Bad query plan decision when using multiple column index - postgresql uses only first column then filters Cosmin Prund 19:52

Jan. 17, 2020

Thread Author Time
Re: proposal: schema variables 📎 Pavel Stehule 21:10

Jan. 21, 2020

Thread Author Time
Re: proposal: schema variables Tomas Vondra 23:41

Jan. 24, 2020

Thread Author Time
Re: proposal: schema variables 📎 Pavel Stehule 05:08

Jan. 26, 2020

Thread Author Time
Re: proposal: schema variables 📎 Pavel Stehule 17:26

Jan. 27, 2020

Thread Author Time
Query optimization advice for beginners Kemal Ortanca 13:15
Re: Query optimization advice for beginners Andreas Kretschmer 13:57
Re: Query optimization advice for beginners Kemal Ortanca 15:33
Re: Query optimization advice for beginners Michael Lewis 16:46

Jan. 28, 2020

Thread Author Time
Re: Query optimization advice for beginners Laurenz Albe 08:37

Jan. 30, 2020

Thread Author Time
Re: Specific query taking time to process Fahiz Mohamed 09:44
Re: Specific query taking time to process Duncan Whitham 12:22
Re: Specific query taking time to process Tom Lane 16:35

Jan. 31, 2020

Thread Author Time
Re: Specific query taking time to process Duncan Whitham 11:01

Browse Archives

Prev | Next
Jump to day: 2 3 4 6 10 13 14 15 16 17 21 24 26 27 28 30 31