Re: no default hash partition - Mailing list pgsql-hackers

From Tom Lane
Subject Re: no default hash partition
Date
Msg-id 18362.1565134512@sss.pgh.pa.us
Whole thread Raw
In response to Re: no default hash partition  (Stephen Frost <sfrost@snowman.net>)
Responses Re: no default hash partition  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
Stephen Frost <sfrost@snowman.net> writes:
> * Tom Lane (tgl@sss.pgh.pa.us) wrote:
>> Hmm.  So given the point about it being hard to predict which hash
>> partitions would receive what values ... under what circumstances
>> would it be sensible to not create a full set of partitions?  Should
>> we just enforce that there is a full set, somehow?

> I imagine there's good reasons this wasn't just done (for this or
> various other things), but couldn't we enforce it by just creating them
> all..?  Sure would simplify a lot of things for users.  Similairly for
> list partitions, I would think.

Well, with lists Alvaro's point holds: you might know a priori that
some of the values are infrequent and don't deserve their own partition.
The thing about hash is that the entries should (in theory) get spread
out to all partitions pretty evenly, so it's hard to see why a user
would want to treat any partition differently from any other.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: partition routing layering in nodeModifyTable.c
Next
From: Stephen Frost
Date:
Subject: Re: no default hash partition