Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id AA1049FA333 for ; Mon, 6 Nov 2006 15:40:55 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 27118-07 for ; Mon, 6 Nov 2006 15:40:51 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from skynet.simkin.ca (skynet.simkin.ca [199.175.137.210]) by postgresql.org (Postfix) with ESMTP id A81599FA1DB for ; Mon, 6 Nov 2006 15:40:51 -0400 (AST) Received: from crecy.medialogik.com (hal.medialogik.com [72.51.27.120]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by skynet.simkin.ca (Postfix) with ESMTP id 7ED90106DD for ; Mon, 6 Nov 2006 11:40:50 -0800 (PST) From: Alan Hodgson Organization: Simkin Network Consulting To: pgsql-php@postgresql.org Subject: Re: PostgreSQL locking from PHP scripts Date: Mon, 6 Nov 2006 11:42:17 -0800 User-Agent: KMail/1.9.1 References: <20061026181147.50048.qmail@web51309.mail.yahoo.com> <200611061105.29055@hal.medialogik.com> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3291794.KSJG9SA20o"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200611061142.17334@hal.medialogik.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/9 X-Sequence-Number: 3627 --nextPart3291794.KSJG9SA20o Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday 06 November 2006 11:16, "Gavin M. Roy" 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,= =20 so pconnect connections are reset at script end. The only difference is=20 connection overhead. I've been trying to find a way around this to allow cursor usage, but there= =20 doesn't seem to be one. =2D-=20 "Thank God we don't get all the government we pay for." -- Will Rogers --nextPart3291794.KSJG9SA20o Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBFT5AZJmf5OzX07HQRAkRMAJ9vGOOYjbq44ttM47F7mmUup5lh3gCdHyRH vy0cq6gfupHWi3ogd+VDCxM= =fzEQ -----END PGP SIGNATURE----- --nextPart3291794.KSJG9SA20o--