Re: Make relcache init write errors not be fatal

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