| From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Possible bug: could not open relation with OID [numbers] SQL State: XX000 |
| Date: | 2017-11-02 03:35:20 |
| Message-ID: | CAMjNa7cq_CWR5wEWS30qxB9umjyMdf55BP75HDfPxgJeWWYgLw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> If that's the correct theory, yes. Did you match up the OID yet?
Yes, I did just now. The OID matches the TOAST table for the temp
table: contract_actual_direct.
This just really surprises me I haven't seen it before considering I
know for a fact that some of my other functions are way more likely to
have their data stored TOASTed, and use the same DROP TABLE pattern at
the end of the function.
Now I suppose i'll have to figure out what to do going forward.
Dropping on commit is not an option, because some of these functions
need to be able to be run multiple times within a transaction.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-11-02 03:45:55 | Re: Possible bug: could not open relation with OID [numbers] SQL State: XX000 |
| Previous Message | Tom Lane | 2017-11-02 03:12:33 | Re: Possible bug: could not open relation with OID [numbers] SQL State: XX000 |