From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Make relcache init write errors not be fatal |
Date: | 2018-12-23 01:54:15 |
Message-ID: | 20181223015415.bpzlkhd2g67njziq@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
On 2018-12-22 20:49:58 -0500, Jeff Janes wrote:
> After running a testing server out of storage, I tried to track down why it
> was so hard to get it back up again. (Rather than what I usually do which
> is just throwing it away and making the test be smaller).
>
> I couldn't start a backend because it couldn't write the relcache init file.
>
> I found this comment, but it did not carry its sentiment to completion:
>
> /*
> * We used to consider this a fatal error, but we might as well
> * continue with backend startup ...
> */
>
> With the attached patch applied, I could at least get a backend going so I
> could drop some tables/indexes and free up space.
Why is this a good idea? It'll just cause hard to debug performance
issues imo.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2018-12-23 02:26:00 | Re: Make relcache init write errors not be fatal |
Previous Message | Jeff Janes | 2018-12-23 01:49:58 | Make relcache init write errors not be fatal |