Re: Query planning on partitioned table causes postgres 13.4 to consume all memory

Duncan Sands <duncan.sands@deepbluecap.com>

From: Duncan Sands <duncan.sands@deepbluecap.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2021-09-20T12:10:17Z
Lists: pgsql-bugs
Hi Tom,

On 19/09/2021 18:03, Tom Lane wrote:
> Duncan Sands <duncan.sands@deepbluecap.com> writes:
>> [ planning DELETE on a thousand-partition table takes forever ]
> 
> FWIW, this situation has been very much improved for v14 [1].

thanks, part (2) of that commit indeed looks like it should solve it.

Best wishes, Duncan.

> In older branches, the best advice I can give you is "don't use
> so many partitions".  Especially not with hash partitioning,
> where the query WHERE clause generally won't translate to any
> useful pruning of the partitions.
> 
> (Personally, I think that hash partitioning is an evil that
> we shouldn't have implemented at all.  Or at least there
> should be stronger warnings about it in the manual than there
> are now.)
> 
> 			regards, tom lane
> 
> [1] https://git.postgresql.org/gitweb/?p=postgresql.git&a=commitdiff&h=86dc90056
> 




Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Doc: further tweaking of v14 release notes.