Martijn van Oosterhout wrote:
Yes, if you're getting that message on a connection without having an
error on that connection then something is really wrong. Note, I've
never used PG with PHP so I can't help you with anything specific.
Turn on pgsql.auto_reset_persistent.
--
Best regards,
Hanne
On Sun, Apr 27, 2008 at 02:05:16PM +0200, Ivan Sergio Borgonovo wrote:
> "Eh?" was my same reaction. I'm going to check the logs... and be
> sure I wasn't dreaming.
> Do you confirm that if I wasn't dreaming and another page that should
> have opened another connection with pg_connect did cause ano
On Sun, 27 Apr 2008 11:26:33 +0200
Martijn van Oosterhout <[EMAIL PROTECTED]> wrote:
> > That would make postgresql a BIG BIG BIG lock.
> > If every rollback is going to block all connections that's a
> > problem. That's exactly why I pointed out that I was using plain
> > pg_connect and not pg_pc
On Sun, Apr 27, 2008 at 11:09:36AM +0200, Ivan Sergio Borgonovo wrote:
> > because each page got an error in a statement inside its
> > transaction. It then issued the above error over and over as you
> > attempted to execute the next statement.
>
> That would make postgresql a BIG BIG BIG lock.
>
On Sat, 26 Apr 2008 20:58:06 -0600
"Scott Marlowe" <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 26, 2008 at 4:19 PM, Ivan Sergio Borgonovo
> <[EMAIL PROTECTED]> wrote:
> >
> > With the added @ everything seemed to be OK.
>
> No, the @ is just making php quietly swallow the postgresql errors
> that a
On Sat, Apr 26, 2008 at 4:19 PM, Ivan Sergio Borgonovo
<[EMAIL PROTECTED]> wrote:
>
> With the added @ everything seemed to be OK.
No, the @ is just making php quietly swallow the postgresql errors
that are being returned. It changes nothing in operation.
> I had to refresh a second time to ge
On Sat, 26 Apr 2008 23:14:07 +0200
Martijn van Oosterhout <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 26, 2008 at 10:52:12PM +0200, Ivan Sergio Borgonovo
> wrote:
> > How am I going to see if the transaction succeeded without
> > checking what happens for each statement and getting the cleanup
> > co
On Sat, Apr 26, 2008 at 10:52:12PM +0200, Ivan Sergio Borgonovo wrote:
> How am I going to see if the transaction succeeded without checking
> what happens for each statement and getting the cleanup code execute?
You basically actually check for the errors in the earlier pg_query()
calls, since th
