Re: PostgreSQL 8.0.6 crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Stark <gsstark(at)mit(dot)edu>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Mark Woodward <pgsql(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: PostgreSQL 8.0.6 crash
Date: 2006-02-09 19:35:34
Message-ID: 3836.1139513734@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Stark <gsstark(at)mit(dot)edu> writes:
> Except not quite, since I think an out of memory error still means that
> backend exits instead of just that query failing.

Not at all! PG will recover from this perfectly well ... if it's given
the opportunity, rather than being SIGKILLed.

> It doesn't seem like a bad idea to have a max_memory parameter that if a
> backend ever exceeded it would immediately abort the current
> transaction.

See ulimit (or local equivalent).

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mark Woodward 2006-02-09 19:49:08 Re: PostgreSQL 8.0.6 crash
Previous Message Greg Stark 2006-02-09 19:31:48 Re: PostgreSQL 8.0.6 crash