| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Chris Travers <chris(at)metatrontech(dot)com>, Cristian Bittel <cbittel(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] BUG #5305: Postgres service stops when closing Windows session |
| Date: | 2010-09-15 17:25:41 |
| Message-ID: | AANLkTinau81rOK=acDHB-FmpmbKRyBanj-OaCEqmwP9H@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Wed, Sep 15, 2010 at 4:03 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> Therefore I cannot give you specific areas where this will happen. Of
> course when systems are low on resources or they are completely
> depleted (100% CPU) things will stop working
Of course. As we all know, degrading gracefully under load is an
unachievable goal.
Anyway, this more or less confirms what I was kind of suspecting all
along: it's hopeless to try to avoid these exit(128) events, so we
just need to look for ways to minimize the impact as much as possible
(i.e. avoid a database PANIC where possible).
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sangmin Ryu | 2010-09-15 18:36:03 | BUG #5658: 'at time zone {timezone description}' can't recognize many time zone abbreviations. |
| Previous Message | Tom Lane | 2010-09-15 14:42:17 | Re: BUG #5655: Composite Type Handles Null Incorrectly |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-09-15 17:30:09 | Re: [HACKERS] Re: pgsql: Use a latch to make startup process wake up and replay |
| Previous Message | Robert Haas | 2010-09-15 17:23:30 | Re: bg worker: patch 1 of 6 - permanent process |