Re: always forced restart after status 139? - Mailing list pgsql-general

From Dominic J. Eidson
Subject Re: always forced restart after status 139?
Date
Msg-id Pine.LNX.4.33.0203181309320.11542-100000@morannon.the-infinite.org
Whole thread Raw
In response to Re: always forced restart after status 139?  ("Jason Williams" <jwilliams@wc-group.com>)
List 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/


pgsql-general by date:

Previous
From: "Jason Williams"
Date:
Subject: Re: always forced restart after status 139?
Next
From: Tom Lane
Date:
Subject: Re: always forced restart after status 139?