From: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PgHacker <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER command reworks |
Date: | 2013-02-04 05:02:24 |
Message-ID: | CADyhKSU84VEdNBNneeOvnPsvG7NEhdowrxEBdaO7tnyh2yB1Lg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2013/2/3 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
>> [ pgsql-v9.3-alter-reworks.3-rename.v10.patch.gz ]
>
> Say ... I hadn't been paying too close attention to this patch, but
> is there any particularly principled reason for it having unified
> only 14 of the 29 object types handled by ExecRenameStmt()?
> If so, how to tell which object types are supposed to be covered?
>
> The reason I'm asking is that it's very unclear to me whether
> https://commitfest.postgresql.org/action/patch_view?id=1043
> (ALTER RENAME RULE) is okay in more-or-less its current form,
> or whether it ought to be bounced back to be reworked for integration
> in this framework.
>
Like trigger or constraint, rule is unavailable to integrate the generic
rename logic using AlterObjectRename_internal().
So, I don't think this patch needs to take much design change.
Thanks,
--
KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2013-02-04 08:55:20 | Re: proposal: ANSI SQL 2011 syntax for named parameters |
Previous Message | Noah Misch | 2013-02-04 03:00:26 | Re: lazy_vacuum_heap()'s removal of HEAPTUPLE_DEAD tuples |