Re: transaction safety - Mailing list pgsql-general

From DaVinci
Subject Re: transaction safety
Date
Msg-id 20010212144306.A954@fangorn.net
Whole thread Raw
In response to RE: transaction safety  (Michael Ansley <Michael.Ansley@intec-telecom-systems.com>)
Responses Re: transaction safety  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Mon, Feb 12, 2001 at 01:08:01PM -0000, Michael Ansley wrote:

> The number returned by the sequence for the serial ID is retained within the
> session, and so it can be returned by calling currval, e.g.:

...[a detailed example]...

> Typically, the insert for a person, and for all the associated addresses
> would be done in the same transaction so that if the insert for one of the
> addresses failed, then the whole lot would role back (perhaps a bit extreme,
> but I think that's what you asked for ;-)

 That sounds good ;)

 I thought it is possible to have different transactions opened and insert
 data in same table from them. It seems my idea was fault, doesn't it?.

 In sumary: locks with inserts are for table and not for tuple. If this is
 not true, tell me details, please :)

 Thanks for all.

                                                                 David

pgsql-general by date:

Previous
From: Michael Ansley
Date:
Subject: RE: transaction safety
Next
From: Tom Lane
Date:
Subject: Re: Error from index "pg_type_typname_index"????