Re: Database Corruption - last chance recovery options?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Best <mbest(at)pendragon(dot)org>
Cc: "Thomas F(dot) O'Connell" <tf(at)o(dot)ptimized(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Database Corruption - last chance recovery options?
Date: 2007-01-06 04:01:18
Message-ID: 26030.1168056078@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Michael Best <mbest(at)pendragon(dot)org> writes:
> Set your memory requirement too high in postgresql.conf, reload instead
> of restarting the database, it silently fails sometime later?

Yeah, wouldn't surprise me, since the reload is going to ignore any
changes related to resizing shared memory. I think that 8.2 might warn
you that it was ignoring the un-applyable changes, but the warnings
would only go to the postmaster log, where they're easily missed :-(

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Geoffrey 2007-01-06 10:01:37 Re: vacuum fails with 'invalid page header' message
Previous Message Tom Lane 2007-01-06 03:12:46 Re: More activity in pg_stat_activity