Re: no default hash partition
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-08-06T22:36:38Z
Lists: pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes: > Given the discussion starting at > https://postgr.es/m/CAFjFpRdBiQjZm8sG9+s0x8Re-afHds6MFLgGuw0wVUNLGrVOQg@mail.gmail.com > we don't have default-partition support with the hash partitioning > scheme. That seems a reasonable outcome, but I think we should have a > comment about it (I had to search the reason for this restriction in the > hash-partitioning patch set). How about the attached? Does anyone see > a reason to make this more verbose, and if so to what? Seems like "it's likely to cause trouble for users" is just going to beg the question "why?". Can we explain the hazard succinctly? Or point to a comment somewhere else that explains it? 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