| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Onder Kalaci <onderk(at)microsoft(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ALTER INDEX .. RENAME allows to rename tables/views as well |
| Date: | 2021-10-06 22:55:49 |
| Message-ID: | E17E5D34-2EEF-48A1-BEF1-DD97EA17403D@amazon.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/6/21, 3:44 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Bossart, Nathan" <bossartn(at)amazon(dot)com> writes:
>> Here's a patch that ERRORs if the object type and statement type do
>> not match. Interestingly, some of the regression tests were relying
>> on this behavior.
>
> ... as, no doubt, are a lot of applications that this will gratuitously
> break. We've long had a policy that ALTER TABLE will work on relations
> that aren't tables, so long as the requested operation is sensible.
Right.
> The situation for "ALTER some-other-relation-kind" is a bit more
> confused, because some cases throw errors and some don't; but I really
> doubt that tightening things up here will earn you anything but
> brickbats. I *definitely* don't agree with discarding the policy
> about ALTER TABLE, especially if it's only done for RENAME.
I think we should at least consider adding this check for ALTER INDEX
since we choose a different lock level in that case.
Nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-10-06 22:58:25 | Re: plperl: update ppport.h and fix configure version check |
| Previous Message | Mark Dilger | 2021-10-06 22:47:27 | Re: BUG #17212: pg_amcheck fails on checking temporary relations |