| From: | "MauMau" <maumau307(at)gmail(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Andres Freund" <andres(at)2ndquadrant(dot)com> |
| Cc: | "Heikki Linnakangas" <hlinnakangas(at)vmware(dot)com>, "PostgreSQL-development" <pgsql-hackers(at)postgreSQL(dot)org>, "Peter Geoghegan" <pg(at)heroku(dot)com>, "Robert Haas" <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Hard limit on WAL space used (because PANIC sucks) |
| Date: | 2013-06-08 23:42:24 |
| Message-ID: | 4B4E81C123184410B92AA8E8EBA73C7A@maumau |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
From: "Joshua D. Drake" <jd(at)commandprompt(dot)com>
> On 06/08/2013 11:27 AM, Andres Freund wrote:
>> You know, the PANIC isn't there just because we like to piss of
>> users. There's actual technical reasons that don't just go away by
>> judging the PANIC as stupid.
>
> Yes I know we aren't trying to piss off users. What I am saying is that it
> is stupid to the user that it PANICS. I apologize if that came out wrong.
I've experienced PANIC shutdown several times due to WAL full during
development. As a user, one problem with PANIC is that it dumps core. I
think core files should be dumped only when "can't happen" events has
occurred like PostgreSQL's bug. I didn't expect postgres dumps core simply
because disk is full. I want postgres to shutdown with FATAL message in
that exact case.
Regards
MauMau
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-06-09 00:09:15 | Re: [COMMITTERS] pgsql: Don't downcase non-ascii identifier chars in multi-byte encoding |
| Previous Message | MauMau | 2013-06-08 23:22:50 | Re: Hard limit on WAL space used (because PANIC sucks) |