Re: performance issue using DBI - Mailing list pgsql-general

From Joshua b. Jore
Subject Re: performance issue using DBI
Date
Msg-id Pine.BSO.4.44.0206061229510.6024-100000@kitten.greentechnologist.org
Whole thread Raw
In response to Re: performance issue using DBI  (Oliver Elphick <olly@lfix.co.uk>)
List pgsql-general
Oh ok. So I was thinking of the way that sequences cut across transactions
and I misinterpreted it. Thanks for the clarification.

Joshua b. Jore ; http://www.greentechnologist.org ; 1121 1233 1311 200
1201 1302 1211 200 1201 1303 200 1300 1233 1313 1211 1302 1212 1311 1230
200 1201 1303 200 1321 1233 1311 1302 200 1211 1232 1211 1231 1321 200
1310 1220 1221 1232 1223 1303 200 1321 1233 1311 200 1201 1302 1211 232
200 1112 1233 1310 1211 200 1013 1302 1211 1211 1232 201 22

On 6 Jun 2002, Oliver Elphick wrote:

> On Thu, 2002-06-06 at 14:55, Joshua b. Jore wrote:u
> >       Don't use currval since some other process might alter the
> > sequence between the time you call nextval and currval.
>
> This is wrong.  currval() will always return the last serial assigned in
> *the*same*session*.  It is not affected by other users at all.
>
> --
> Oliver Elphick                                Oliver.Elphick@lfix.co.uk
> Isle of Wight                              http://www.lfix.co.uk/oliver
> GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839  932A 614D 4C34 3E1D 0C1C
>
>      "Therefore being justified by faith, we have peace with
>       God through our Lord Jesus Christ."       Romans 5:1
>


pgsql-general by date:

Previous
From: jtp
Date:
Subject: ssl
Next
From: pblunat
Date:
Subject: a trigger question