Re: Cannot start Postgres- FATAL: invalid cache id: 19

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Vick Khera <vivek(at)khera(dot)org>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Subject: Re: Cannot start Postgres- FATAL: invalid cache id: 19
Date: 2010-12-01 15:50:49
Message-ID: 16526.1291218649@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Vick Khera <vivek(at)khera(dot)org> writes:
> On Wed, Dec 1, 2010 at 9:20 AM, Jolles, Peter M (GE Energy)
> <peter(dot)jolles(at)ge(dot)com> wrote:
>> 2010-11-29 12:39:17 EST HINT: Stop the postmaster and use a standalone
>> backend to vacuum that database.

> so did you do what the HINT told you to do? does it still not startup?

This is the second report we've seen of relatively new 9.0 installations
shutting down due to wraparound (the other was bug #5718). I find this
disturbing. If we're lucky, the cause is already fixed:
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=b58c25055ef6d7097618c680f6768689a110d529
but if that's the only contributing factor then why weren't we seeing
similar reports about 8.3 and 8.4? I'm worried that there is some
other bug in 9.0 autovacuum. Has anyone stress-tested 9.0 to see if
autovacuum manages to keep the wraparound threshold moving forward?

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Samba 2010-12-01 15:51:06 [REPOST] plpgsql : looping over multidimensional array : getting NULL for subdimension
Previous Message Tom Lane 2010-12-01 15:43:24 Re: Stalled post to pgsql-general