| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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:52:33 |
| Message-ID: | 20060209195233.GC7693@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark wrote:
> Well in a way it does. Postgres would get an out-of-memory error from malloc
> which it would handle properly and the world would be happy.
>
> 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 -- the transaction is aborted, but the backend can continue
working perfectly fine.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2006-02-09 19:53:44 | Re: PostgreSQL 8.0.6 crash |
| Previous Message | Tom Lane | 2006-02-09 19:51:50 | Re: User Defined Types in Java |