On Wed, Sep 15, 2010 at 4:03 AM, Dave Page <dp...@pgadmin.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

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Reply via email to