| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: no default hash partition |
| Date: | 2019-08-06 22:36:38 |
| Message-ID: | 15693.1565130998@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2019-08-06 22:45:06 | Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS) |
| Previous Message | Alvaro Herrera | 2019-08-06 22:27:35 | no default hash partition |