| From: | "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | "Mark Steben" <msteben(at)autorevenue(dot)com> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Error on CLUSTER command |
| Date: | 2008-02-08 19:49:50 |
| Message-ID: | dcc563d10802081149u63382b34yabac79461003ddf6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Feb 8, 2008 1:37 PM, Mark Steben <msteben(at)autorevenue(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2008-02-08 20:54:52 | Re: pg_dump on windows |
| Previous Message | Mark Steben | 2008-02-08 19:37:02 | Re: Error on CLUSTER command |