| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jan Wieck <JanWieck(at)yahoo(dot)com> |
| Cc: | ryan <ryan(at)bel(dot)bc(dot)ca>, pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)orgg |
| Subject: | Re: [HACKERS] Foreign key bugs (Re: "New" bug?? Serious - crashes backend.) |
| Date: | 2000-07-11 21:22:43 |
| Message-ID: | 24540.963350563@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
JanWieck(at)t-online(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2000-07-11 21:30:06 | Re: Foreign key bugs + other problems |
| Previous Message | Stephan Szabo | 2000-07-11 20:44:05 | Re: Foreign key bugs + other problems |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-07-11 21:27:44 | Re: update on TOAST status' |
| Previous Message | Andrew McMillan | 2000-07-11 21:10:51 | Re: Re: postgres TODO |