Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.)
| От | JanWieck@t-online.de (Jan Wieck) |
|---|---|
| Тема | Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.) |
| Дата | |
| Msg-id | 200007111847.UAA19282@hot.jw.home обсуждение исходный текст |
| Ответ на | Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.) (Tom Lane <tgl@sss.pgh.pa.us>) |
| Ответы |
Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.)
|
| Список | pgsql-bugs |
Tom Lane wrote:
>
> >> but a larger question is why the system let you drop a table that
> >> is the target of a referential integrity check (which I assume is
> >> what you did to get into this state).
>
> > For me too.
>
> What about renaming as opposed to dropping? Since the triggers are set
> up to use names rather than OIDs, seems like they are vulnerable to a
> rename. Maybe they should be using table OIDs in their parameter lists.
> (That'd make pg_dump's life harder however...)
That at least shows how he might have gotten there. And yes,
they need to either keep track of renamings or use OID's.
Jan
--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck@Yahoo.com #
В списке pgsql-bugs по дате отправления: