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 4665.1168107602@sss.pgh.pa.us
Whole thread Raw
In response to Re: Database Corruption - last chance recovery options?  ("Thomas F. O'Connell" <tf@o.ptimized.com>)
List pgsql-general
"Thomas F. O'Connell" <tf@o.ptimized.com> writes:
>> 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?

> Wait, now I'm curious. If a change in postgresql.conf that requires a
> restart doesn't take effect on reload, then how could a related
> failure manifest at all, regardless of when?

The point is that when you eventually shut down and restart the
postmaster, it'd fail then ... perhaps long after you've forgotten
about your configuration changes, so it might be a bit mystifying.

            regards, tom lane

pgsql-general by date:

Previous
From: "Thomas F. O'Connell"
Date:
Subject: Re: Database Corruption - last chance recovery options?
Next
From: John McCawley
Date:
Subject: Re: Database versus filesystem for storing images