| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Harold Giménez <harold(dot)gimenez(at)gmail(dot)com> |
| Cc: | Peter Geoghegan <pg(at)heroku(dot)com>, Daniel Farina <daniel(at)heroku(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Redesigning checkpoint_segments |
| Date: | 2013-06-06 07:16:11 |
| Message-ID: | 51B0373B.3030407@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2013-06-06 07:21:13 | Re: Redesigning checkpoint_segments |
| Previous Message | Dean Rasheed | 2013-06-06 07:09:37 | Re: how to find out whether a view is updatable |