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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Duncan Sands <duncan(dot)sands(at)deepbluecap(dot)com>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Query planning on partitioned table causes postgres 13.4 to consume all memory
Date: 2021-09-19 16:03:04
Message-ID: 1556207.1632067384@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Duncan Sands <duncan(dot)sands(at)deepbluecap(dot)com> writes:
> [ planning DELETE on a thousand-partition table takes forever ]

FWIW, this situation has been very much improved for v14 [1].
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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Noah Misch 2021-09-20 04:41:43 Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Previous Message Tom Lane 2021-09-19 15:08:29 Re: BUG #17195: Can't bind $1::int param when I use COPY TO STDOUT statement - libpq, C++