Re: too many Fatal Error 1: shutdown messages

From: "Bjoern Metzdorf" <bm(at)turtle-entertainment(dot)de>
To: "Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: too many Fatal Error 1: shutdown messages
Date: 2003-01-08 23:57:08
Message-ID: 024901c2b771$a84cfb40$0564a8c0@toolteam.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> "Johnson, Shaunn" <SJohnson6(at)bcbsm(dot)com> writes:
> > Running PostgreSQL 7.2.1 on RedHat Linux 7.2
>
> > FATAL 2: open of /var/lib/pgsql/data/pg_clog/0003 failed: No such file
or
> > directory
> > server closed the connection unexpectedly
>
> You've run into one of the bugs that we fixed in 7.2.3.
>
> I am not sure if you can recover from this :-( Do you have a recent
> backup?

We've run into these pg_clog issues quite a lot in the last time with 7.2.1.
Good to know that 7.2.3 might fix this.

In my experience you don't necessarily need to grab the latest backup. If
you really just want to get the database up and running again, you may use a
dummy clog and then dump and restore the database.

E.g. "dd if=/dev/zero of=/path/to/pgdata/pg_clog/0003 bs=1024k count=256"

Tom pointed that out in
http://groups.google.com/groups?q=tom+lane+pg_clog&hl=en&lr=&ie=UTF-8&oe=utf
-8&selm=27106.1031148278%40sss.pgh.pa.us&rnum=5

Regards,
Bjoern

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joseph Shraibman 2003-01-09 00:26:33 Re: Character Encoding WAS: ArrayIndexOutOfBoundsException in Encoding.decodeUTF8()
Previous Message Joseph Shraibman 2003-01-08 23:31:07 Character Encoding WAS: ArrayIndexOutOfBoundsException in Encoding.decodeUTF8()