Hello All
I recently ran out of disk space on the volume hosting my default
tablespace. As it turned out, the sysad didnt allocate all of the disk to
the volume when he installed it, so he resized the volume and restarted the
database. The server came up fine so I assumed all was well ( the
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
lo_creat fails with:
ERROR: large object oid already exists
Well, does it?
What PG version is this? I'm suspicious that it's pre-8.1 and the
problem is that your OID counter has wrapped around to a region that
is already pretty densely
Tom
You hit the nail on the head actually! Further delving into the issue
revealed that but I hadnt had a chance to post.
We recently used copy to put some lobs back into the database, about 70k of
them. All of these lobs were assigned sequential oids incremented by 1. We
then wrapped around
Thank you both!! That got me back up and running ( for now ). Hopefully
this will give me enough enough time to finish the migration next week.
Thanks again!!
On Jan 4, 2008 4:21 PM, Alvaro Herrera [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Is there anyway to force 8.0 to start at
[EMAIL PROTECTED] wrote:
Is there anyway to force 8.0 to start at a specific value? That would at
least get us back up and running.
Stop the system (cleanly) and use pg_resetxlog -o.
--
Alvaro Herrerahttp://www.CommandPrompt.com/
PostgreSQL Replication,
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
Is there anyway to force 8.0 to start at a specific value? That would at
least get us back up and running.
You're in luck: 8.0's pg_resetxlog has the -o switch, so just shut down
(cleanly), use pg_resetxlog to put the OID counter where you want it,
