| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Robert Haas <rhaas(at)postgresql(dot)org> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [COMMITTERS] pgsql: Implement table partitioning. |
| Date: | 2017-10-18 01:00:35 |
| Message-ID: | c2731d90-84be-8c27-7393-46617ad0581c@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On 2017/10/18 1:52, Alvaro Herrera wrote:
> Alvaro Herrera wrote:
>> Robert Haas wrote:
>>> Implement table partitioning.
>>
>> Is it intentional that you can use ALTER TABLE OWNER TO on the parent
>> table, and that this does not recurse to modify the partitions' owners?
>> This doesn't seem to be mentioned in comments nor documentation, so it
>> seems an oversight to me.
Hmm, I would say of it that the new partitioning didn't modify the
behavior that existed for inheritance.
That said, I'm not sure if the lack of recursive application of ownership
change to descendant tables is unintentional.
> The alter table docs say that ONLY must be specified if one does not
> want to modify descendants, so I think this is a bug.
Just to clarify, if we do think of it as a bug, then it will apply to the
inheritance case as well, right?
Thanks,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-10-18 08:53:23 | Re: [COMMITTERS] pgsql: Implement table partitioning. |
| Previous Message | Peter Eisentraut | 2017-10-17 20:20:50 | pgsql: Don't use SGML empty tags |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-10-18 01:49:45 | Re: Re: Is anything preventing us from allowing write to foreign tables from standby? |
| Previous Message | Amit Langote | 2017-10-18 00:43:43 | alter table doc fix |