From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Alex Pilosov <alex(at)pilosoft(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: bug: alter table/FK |
Date: | 2000-10-17 15:58:14 |
Message-ID: | Pine.BSF.4.10.10010170849310.76155-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Under current sources, it no longer crashes, it just elogs now
after Tom's changes. When I get more time I'd like to put in a
more complete solution (possibly moving to oids rather than names
in the argument list in the process). There are alot of other related
problems (rename column, check constraint dumping after column/table
renames, dropping objects that refer to other objects that have
been removed, drop ... restrict vs cascade)
On Tue, 17 Oct 2000, Alex Pilosov wrote:
> I don't know if this has been fixed or not, but alter table will not
> adjust RI/FK triggers on the table.
>
> I.E:
>
> create table foo (a int4 primary key)
> create table bar (b int4 references foo)
> alter table foo rename to foo2
>
> now, updates to foo will either crash or hang postgres.
>
>
> What needs to be done: on alter table, update tgargs in pg_trigger table
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-10-17 16:04:38 | Re: pgsql/doc (FAQ_MSWIN INSTALL_MSWIN) |
Previous Message | Tom Lane | 2000-10-17 15:51:26 | Re: incompatible changes of PQsetdbLogin() |