Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.) - Mailing list pgsql-bugs

From JanWieck@t-online.de (Jan Wieck)
Subject Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.)
Date
Msg-id 200007111847.UAA19282@hot.jw.home
Whole thread Raw
In response to Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.)  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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 by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.)
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.)