From: Scott Marlowe <scott.marlowe@gmail.com>
To: Mark Steben <msteben@autorevenue.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Error on CLUSTER command
Date: Fri, 8 Feb 2008 13:49:50 -0600
Message-ID: <dcc563d10802081149u63382b34yabac79461003ddf6@mail.gmail.com> (raw)
In-Reply-To: <00bf01c86a89$fa4af7a0$14010a0a@dei26g028575>
References: <2025.1202488530@sss.pgh.pa.us>
<00bf01c86a89$fa4af7a0$14010a0a@dei26g028575>
On Feb 8, 2008 1:37 PM, Mark Steben <msteben@autorevenue.com> wrote:
> 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?
On 7.4 I'd say you'd be better off dumping and reloading all your data
than playing with pg_resetxlog on a live database. Might as well
update to 7.4.19 while you're at it.
I'd run a dump restore to a test machine running 7.4.19 first to make
sure it will go well, or get another server that can handle the load,
or make a new 7.4.19 instance on the same machine and transfer to
that. But if it's a production database I wouldn't run pg_resetxlog
on it myself.
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: scott.marlowe@gmail.com, msteben@autorevenue.com, tgl@sss.pgh.pa.us
Subject: Re: Error on CLUSTER command
In-Reply-To: <dcc563d10802081149u63382b34yabac79461003ddf6@mail.gmail.com>
* 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