Re: PostgreSQL locking from PHP scripts

From: Alan Hodgson <ahodgson(at)simkin(dot)ca>
To: pgsql-php(at)postgresql(dot)org
Subject: Re: PostgreSQL locking from PHP scripts
Date: 2006-11-06 19:42:17
Message-ID: 200611061142.17334@hal.medialogik.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-php

On Monday 06 November 2006 11:16, "Gavin M. Roy" <gmr(at)ehpg(dot)net> wrote:
> Well you can use persistent connections. Instead of pg_connect use
> pg_pconnect. I don't know if it will keep the lock or not, I've not
> tested, but it seems like you'd need a pretty elaborate connection
> management setup to make sure you're locking and unlocking the
> records for the right client.

No, it won't. pconnect and connect are guaranteed to work the same by PHP,
so pconnect connections are reset at script end. The only difference is
connection overhead.

I've been trying to find a way around this to allow cursor usage, but there
doesn't seem to be one.

--
"Thank God we don't get all the government we pay for." -- Will Rogers

In response to

Browse pgsql-php by date

  From Date Subject
Next Message Herbie McDuck 2006-11-07 00:45:18 Re: PostgreSQL locking from PHP scripts
Previous Message Gavin M. Roy 2006-11-06 19:16:51 Re: PostgreSQL locking from PHP scripts