Re: no default hash partition
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephen Frost <sfrost@snowman.net>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-08-06T23:35:12Z
Lists: 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
Commits
-
Clarify the default partition's role
- 956451e8bc9f 13.0 landed
- edc793d374af 12.0 landed
- bf6455d4c557 11.6 landed
-
Add comment on no default partition with hash partitioning
- 12afc7145c03 13.0 landed