Re: Hard limit on WAL space used (because PANIC sucks) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Hard limit on WAL space used (because PANIC sucks)
Date
Msg-id 17460.1390341070@sss.pgh.pa.us
Whole thread Raw
In response to Re: Hard limit on WAL space used (because PANIC sucks)  (Greg Stark <stark@mit.edu>)
Responses Re: Hard limit on WAL space used (because PANIC sucks)  (Kevin Grittner <kgrittn@ymail.com>)
List pgsql-hackers
Greg Stark <stark@mit.edu> writes:
> Fwiw I think "all transactions lock up until space appears" is *much*
> better than PANICing. Often disks fill up due to other transient
> storage or people may have options to manually increase the amount of
> space. it's much better if the database just continues to function
> after that rather than need to be restarted.

Well, PANIC is certainly bad, but what I'm suggesting is that we just
focus on getting that down to ERROR and not worry about trying to get
out of the disk-shortage situation automatically.  Nor do I believe
that it's such a good idea to have the database freeze up until space
appears rather than reporting errors.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [9.3 bug] disk space in pg_xlog increases during archive recovery
Next
From: Tom Lane
Date:
Subject: Re: Incorrectly reporting config errors