Re: fd.c doesn't remove files on a crash-restart

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: fd.c doesn't remove files on a crash-restart
Date: 2016-03-16 18:06:23
Message-ID: 56E9A09F.5040202@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/16/2016 11:04 AM, Andres Freund wrote:
> On 2016-03-16 11:02:09 -0700, Joshua D. Drake wrote:
>>>> 3. The problem can get worse over time. If you have a very long running
>>>> instance, any time the backend crash-restarts you have to potential to
>>>> increase disk space used for no purpose.
>>>
>>> But I think these outweigh the debugging benefit.
>>
>> Well as Andrew said, we could also create postmaster start option that
>> defaults to don't save.
>
> I think these days you'd simply use restart_after_crash = false. For
> debugging I found that to be rather valuable.

That would have created an extended outage for this installation. I am
not sure we can force that for something that should not happen in the
first place (filling up the hard drive with dead files).

JD

>
>
> Andres
>
>

--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joshua D. Drake 2016-03-16 18:07:06 Re: fd.c doesn't remove files on a crash-restart
Previous Message Julien Rouhaud 2016-03-16 18:05:50 Re: Choosing parallel_degree