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

"D. Dante Lorenso" <dante@lorenso.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