| From: | "Dominic J(dot) Eidson" <sauron(at)the-infinite(dot)org> |
|---|---|
| To: | Jason Williams <jwilliams(at)wc-group(dot)com> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: always forced restart after status 139? |
| Date: | 2002-03-18 19:10:22 |
| Message-ID: | Pine.LNX.4.33.0203181309320.11542-100000@morannon.the-infinite.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 18 Mar 2002, Jason Williams wrote:
> Point taken and understood.
You might wanna fix those extensions so they don't crash, btw :)
> The problem is this: we are planning to make this database for a commercial
> website that will handle financial transactions. What will happen if the
> database receives a seg fault and another user of the database is in the
> middle of submitting a "critical" update? I'm assuming it will rollback
> gracefully?
It should roll back to it's pre-transaction state.
--
Dominic J. Eidson
"Baruk Khazad! Khazad ai-menu!" - Gimli
-------------------------------------------------------------------------------
http://www.the-infinite.org/ http://www.the-infinite.org/~dominic/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-03-18 19:47:17 | Re: always forced restart after status 139? |
| Previous Message | Jason Williams | 2002-03-18 19:00:26 | Re: always forced restart after status 139? |