| From: | Jeff Frost <jeff(at)frostconsultingllc(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: update before drop causes OID problems in transaction? |
| Date: | 2006-03-17 22:55:01 |
| Message-ID: | Pine.LNX.4.64.0603171454170.11424@discord.dyndns.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Fri, 17 Mar 2006, Tom Lane wrote:
> Jeff Frost <jeff(at)frostconsultingllc(dot)com> writes:
>> After commit, I get a lovely:
>> ERROR: could not open relation with OID x
>
> Could we see a complete test case, rather than handwaving? I'd expect
> some issues like this if you were using any prepared statements or
> plpgsql functions with non-EXECUTEd queries involving the dropped table,
> but your description doesn't mention either of those risk factors.
Tom, it's for a client, so let me see if they'll allow me to post the
transaction, if not, I'll have to write something equivalent. More later.
--
Jeff Frost, Owner <jeff(at)frostconsultingllc(dot)com>
Frost Consulting, LLC http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Frost | 2006-03-18 04:20:33 | Re: update before drop causes OID problems in transaction? |
| Previous Message | Tom Lane | 2006-03-17 22:52:49 | Re: update before drop causes OID problems in transaction? |