| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: no default hash partition |
| Date: | 2019-08-07 16:25:02 |
| Message-ID: | 20190807162502.GA28350@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-Aug-06, Stephen Frost wrote:
> Yeah, that's a fair argument, but giving the user a way to say that
> would address it. As in, "create me a list-partitioned table for these
> values, plus a default." Anyhow, I'm sure that I'm taking this beyond
> what we need to do right now, just sharing where I think it'd be good
> for things to go.
Fabien Coelho already submitted a patch for this IIRC.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-08-07 16:28:22 | Rethinking opclass member checks and dependency strength |
| Previous Message | Konstantin Knizhnik | 2019-08-07 16:23:34 | Re: Removing unneeded self joins |