From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)atentus(dot)com> |
Cc: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, pgsql-patches(at)postgresql(dot)org |
Subject: | Re: [HACKERS] pg_attribute.attisinherited ? |
Date: | 2002-08-26 14:26:01 |
Message-ID: | 22864.1030371961@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Alvaro Herrera <alvherre(at)atentus(dot)com> writes:
> I'm thinking about the ONLY part in the grammar in ALTER TABLE... DROP
> COLUMN and RENAME COLUMN. I think they should not be there:
Local DROP COLUMN is fine: it just causes the column to become
non-inherited in any children. (Your patch for attisinherited will
need to cover this case.)
Local RENAME COLUMN does need to be prohibited, as does local ADD
COLUMN, as does local ALTER COLUMN if we ever allow changing column
type. Basically we need to prohibit the column from becoming
incompatible with its children.
I don't agree with the notion of changing the grammar to achieve that,
btw. Simpler and more friendly to add a specific error check in
(most likely place) utility/tcop.c. Then if you try to say ONLY you'll
get a more useful complaint than "parse error".
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Sir Mordred The Traitor | 2002-08-26 14:46:19 | @(#)Mordred Labs advisory 0x0007: Remove DoS in PostgreSQL |
Previous Message | Alessio Bragadini | 2002-08-26 14:21:04 | Re: Release of v7.2.2 (Was: Re: @(#)Mordred Labs ad...) |
From | Date | Subject | |
---|---|---|---|
Next Message | Gerhard Hintermayer | 2002-08-26 14:40:52 | Re: libpgtcl modifications |
Previous Message | Tom Lane | 2002-08-26 14:00:48 | Re: [HACKERS] TODO Done. Superuser backend slot reservations |