Postgres Pro
Downloads
Home   >   mailing lists

Re: huge memory of Postgresql backend process - Mailing list pgsql-bugs

From David Rowley
Subject Re: huge memory of Postgresql backend process
Date
Msg-id CAApHDvoSOQpgxXnCDH1wZ9xmR+XmQprMBAJ09tVYrA2JezqhmQ@mail.gmail.com
Whole thread Raw
In response to Re: huge memory of Postgresql backend process  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: huge memory of Postgresql backend process
List pgsql-bugs
Tree view 
On Fri, 9 Sept 2022 at 01:48, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Moreover, HASH partitioning is effectively incapable of being
> pruned, so that every query is going to touch every partition.
> (IMO, hash partitioning is basically never a good idea.)

I think that might have only briefly been true during the v11 cycle,
but by the time the release came we had hash partition and partition
pruning.

David

pgsql-bugs by date:

Previous
From: David Rowley
Date:
Subject: Re: huge memory of Postgresql backend process
Next
From: Japin Li
Date:
Subject: Re: BUG #17610: Use of multiple composite types incompatible with record-typed function parameter