pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mark Steben <msteben@autorevenue.com>
To: 'Tom Lane' <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Error on CLUSTER command
Date: Fri, 8 Feb 2008 14:37:02 -0500
Message-ID: <00bf01c86a89$fa4af7a0$14010a0a@dei26g028575> (raw)
In-Reply-To: <2025.1202488530@sss.pgh.pa.us>

The doc says to do an initdb and reload the data whenever you run
pg_resetxlog.  Do you concur with that even if we are only resetting the OID
counter?

-----Original Message-----
From: Tom Lane [mailto:tgl@sss.pgh.pa.us] 
Sent: Friday, February 08, 2008 11:36 AM
To: Mark Steben
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Error on CLUSTER command 

"Mark Steben" <msteben@autorevenue.com> writes:
> The number may change pointing to another index or stay the same.
> The error persists if I repeat 3 or 4 times.  Usually after the
> 4th or 5th time the cluster is successful.

Hm.  I'd guess that the installation is old enough that the OID counter
has wrapped around, and is currently in a region that is pretty densely
populated with existing tables.  (You could check that out by looking
into the database directory.)  7.4.x doesn't have the logic that was
added later to skip over filenames that are already in use; instead
you just get an error if there's a collision.

I forget whether 7.4's pg_resetxlog has an option to set the OID
counter, but if it does then a temporary fix is to move the OID counter
to some less densely populated range.

> What is the risk of performing an upgrade to 7.4.19?

Low, but it won't make this particular problem go away.

			regards, tom lane




view thread (7+ messages)  latest in thread

Message-ID: <00bf01c86a89$fa4af7a0$14010a0a@dei26g028575>
Permalink:  ../00bf01c86a89$fa4af7a0$14010a0a@dei26g028575/
Also on:    postgresql.org/message-id/00bf01c86a89$fa4af7a0$14010a0a@dei26g028575

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: msteben@autorevenue.com, tgl@sss.pgh.pa.us
  Subject: Re: Error on CLUSTER command
  In-Reply-To: <00bf01c86a89$fa4af7a0$14010a0a@dei26g028575>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox