| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [COMMITTERS] pgsql: Implement table partitioning. |
| Date: | 2017-10-18 16:39:52 |
| Message-ID: | 27080.1508344792@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Oct 18, 2017 at 4:53 AM, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
>> My view is that the fact that partitioning uses inheritance is just an
>> implementation detail. We shouldn't let historical behavior for
>> inheritance dictate behavior for partitioning. Inheritance has many
>> undesirable warts.
> I don't think it's a good idea for table partitioning and table
> inheritance to behave differently.
I'm with Robert on this one. I'd be in favor of changing both cases
to make ALTER OWNER recurse by default.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-10-18 16:58:27 | Re: [COMMITTERS] pgsql: Implement table partitioning. |
| Previous Message | Robert Haas | 2017-10-18 16:35:13 | Re: [COMMITTERS] pgsql: Implement table partitioning. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2017-10-18 16:48:55 | Re: SIGSEGV in BRIN autosummarize |
| Previous Message | Robert Haas | 2017-10-18 16:35:13 | Re: [COMMITTERS] pgsql: Implement table partitioning. |