Re: SELECT ... FOR UPDATE performance costs? alternatives?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "D(dot) Dante Lorenso" <dante(at)lorenso(dot)com>
Cc: Douglas McNaught <doug(at)mcnaught(dot)org>, Erik Jones <erik(at)myemma(dot)com>, btober(at)ct(dot)metrocast(dot)net, pgsql-general(at)postgresql(dot)org
Subject: Re: SELECT ... FOR UPDATE performance costs? alternatives?
Date: 2007-08-16 23:15:52
Message-ID: 14056.1187306152@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"D. Dante Lorenso" <dante(at)lorenso(dot)com> writes:
> Douglas McNaught wrote:
>> How quickly after you update the row status are you comitting (and
>> releasing locks)?

> I am calling a stored proc from PHP. Since I do not begin a
> transaction, I assume that my call is automatically committed
> immediately after invocation.

Have you actually verified that, or are you just assuming it?
I believe that PHP has some sort of autocommit on/off option,
which might possibly be doing things behind your back.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message D. Dante Lorenso 2007-08-16 23:33:25 Re: SELECT ... FOR UPDATE performance costs? alternatives?
Previous Message rakesh kumar 2007-08-16 23:03:57 some information