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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.)
Дата
Msg-id 24540.963350563@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.)  (JanWieck@t-online.de (Jan Wieck))
Список pgsql-bugs
JanWieck@t-online.de (Jan Wieck) writes:
> Tom Lane wrote:
>> 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.

I got mail from Ryan earlier admitting that he'd hand-edited a dump file
and reloaded it, so that was how his triggers got out of sync with the
table names.  But still, it sounds like we need to fix the RENAME case.

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: JanWieck@t-online.de (Jan Wieck)
Дата:
Сообщение: Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.)
Следующее
От: Philip Warner
Дата:
Сообщение: Re: [HACKERS] Re: [SQL] MAX() of 0 records.