Re: Database Corruption - last chance recovery options? - Mailing list pgsql-general

From Tom Lane
Subject Re: Database Corruption - last chance recovery options?
Date
Msg-id 26030.1168056078@sss.pgh.pa.us
Whole thread Raw
In response to Re: Database Corruption - last chance recovery options?  (Michael Best <mbest@pendragon.org>)
Responses Re: Database Corruption - last chance recovery options?
List pgsql-general
Michael Best <mbest@pendragon.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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: More activity in pg_stat_activity
Next
From: Geoffrey
Date:
Subject: Re: [ADMIN] vacuum fails with 'invalid page header' message