| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Christopher Sawtell <csawtell(at)xtra(dot)co(dot)nz> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Minor disaster after upgrading with cvs. |
| Date: | 2001-03-15 15:53:57 |
| Message-ID: | 13870.984671637@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Christopher Sawtell <csawtell(at)xtra(dot)co(dot)nz> writes:
> I've just - about 4 hours ago upgraded via cvsup and upon restarting PG
> I was greated by this gem of information
> 02:10:26 postgres(at)berty:~ $ ./bin/pg_ctl -o -i start
> postmaster successfully started
> 02:10:43 postgres(at)berty:~ $ FATAL 2: database was initialized with
> PG_CONTROL_VERSION 0,
> but the backend was compiled with PG_CONTROL_VERSION 71.
> looks like you need to initdb.
Ah, you have not been paying attention to pghackers (always a good idea
when running CVS tip ;-)). You need to run the new contrib utility
contrib/pg_resetxlog to update the format of your pg_control and WAL
files.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Masto | 2001-03-15 16:11:26 | Re: Fast Inserts and Hardware Questions |
| Previous Message | Gregory Bittar | 2001-03-15 15:43:05 | Re: shared memory settings: SHMMAX and SHMALL |