Re: Redesigning checkpoint_segments - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Redesigning checkpoint_segments
Date
Msg-id 51B0373B.3030407@commandprompt.com
Whole thread Raw
In response to Re: Redesigning checkpoint_segments  (Harold Giménez <harold.gimenez@gmail.com>)
List pgsql-hackers
On 6/5/2013 11:25 PM, Harold Giménez wrote:

Instead of "running out of disk space PANIC" we should just write to an emergency location within PGDATA

This merely buys you some time, but with aggressive and sustained write throughput you are left on the same spot. Practically speaking it's the same situation as increasing the pg_xlog disk space.

Except that you likely can't increase pg_xlog space (easily). The point here is to have overflow, think swap space.

I agree it is better than PANIC, but read-only mode is definitely also a form of throttling; a much more abrupt and unfriendly one if I may add.


I would think read only is less unfriendly than an all out failure. Consider if done correctly, the database would move back into read-write mode once the problem was resolved.

JD


pgsql-hackers by date:

Previous
From: Dean Rasheed
Date:
Subject: Re: how to find out whether a view is updatable
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Redesigning checkpoint_segments