Re: parse partition strategy string in gram.y - Mailing list pgsql-hackers

From Tom Lane
Subject Re: parse partition strategy string in gram.y
Date
Msg-id 3930526.1666659024@sss.pgh.pa.us
Whole thread Raw
In response to Re: parse partition strategy string in gram.y  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
Responses Re: parse partition strategy string in gram.y  ("Finnerty, Jim" <jfinnert@amazon.com>)
Re: parse partition strategy string in gram.y  ("Finnerty, Jim" <jfinnert@amazon.com>)
List pgsql-hackers
Alvaro Herrera <alvherre@alvh.no-ip.org> writes:
> On 2022-Oct-24, Finnerty, Jim wrote:
>> The advantage of hash partition bounds is that they are not
>> domain-specific, as they are for ordinary RANGE partitions, but they
>> are more flexible than MODULUS/REMAINDER partition bounds.

I'm more than a bit skeptical of that claim.  Under what
circumstances (other than a really awful hash function,
perhaps) would it make sense to not use equi-sized hash
partitions?  If you can predict that more stuff is going
to go into one partition than another, then you need to
fix your hash function, not invent more complication for
the core partitioning logic.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Crash after a call to pg_backup_start()
Next
From: Julien Rouhaud
Date:
Subject: Re: [PATCHES] Post-special page storage TDE support