Re: page 1 of relation global/11787 was uninitialized

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: "Stephen R(dot) van den Berg" <srb(at)cuci(dot)nl>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: page 1 of relation global/11787 was uninitialized
Date: 2013-04-09 17:38:26
Message-ID: 20130409173826.GD27905@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2013-04-09 19:30:38 +0200, Andres Freund wrote:
> On 2013-04-09 19:18:57 +0200, Stephen R. van den Berg wrote:
> > Tom Lane wrote:
> > >"Stephen R. van den Berg" <srb(at)cuci(dot)nl> writes:
> > >> Just today one of my systems experienced a kernel panic, and halted abruptly.
> > >> Running Linux 3.1.9, PostgreSQL 9.0.4 (Debian 9.0.4-1+b1, to be precise).
> >
> > >It's conceivable that updating to something more current than 9.0.4
> > >would get you out of this --- we've fixed quite a number of WAL replay
> > >bugs in the last two years.
> >
> > I see that there is a 9.0.13, but that would be a source upgrade, since Debian
> > doesn't provide later than 9.0.4 AFAICS.
>
> Afaik debian has never shipped 9.0 in any stable release at all. You can
> use the packages provided by the postgres community though, they are
> compatible:
> http://wiki.postgresql.org/wiki/Apt
>
> > I suppose upgrading to 9.1.9 is not recommended in this state, or is
> > it?
>
> You can at least try, don't think it will make more problems than you
> already have.

Uh, I didn't read careful enough. I thought you were talking about
upgrading to the newest 9.0 release which *does* make sense.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen R. van den Berg 2013-04-09 17:40:47 Re: page 1 of relation global/11787 was uninitialized
Previous Message Andres Freund 2013-04-09 17:37:34 Re: page 1 of relation global/11787 was uninitialized