| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: oids |
| Date: | 2008-02-11 18:45:45 |
| Message-ID: | 20080211184545.GC953@crankycanuck.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, Feb 11, 2008 at 10:38:55AM -0800, Bob Pawley wrote:
> All of my tables are without oids.
>
> I have an application in which I drop, then recreate a table (to reset
> serial numbers) and with an update on the new information I get an error
> about a specific oid missing.
>
> Any thoughts would be appreciated.
Your application has the plan for accessing that table cached, and the way
the access happens "under the hood" is by the oid of the table. This is the
"table oid" that someone upthread was mentioning.
There's probably a less kludgey way of resetting serial numbers. Is this a
sequence? What's wrong with setval()?
A
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2008-02-11 18:46:44 | Re: oids |
| Previous Message | Bob Pawley | 2008-02-11 18:38:55 | Re: oids |