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.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
