Re: php with postgres - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: php with postgres
Date
Msg-id 200307221735.h6MHZRL03006@candle.pha.pa.us
Whole thread Raw
In response to Re: php with postgres  (Thomas Swan <tswan@idigx.com>)
List pgsql-hackers
Thomas Swan wrote:
> >>Oh, I remember that now as part of the persistent connection code.  As I
> >>remember, we told them to do BEGIN;COMMIT; to clear any open transaction
> >>state passed to the new client.  Is that in there?  If not, it has to be
> >>added too.  ROLLBACK will generate an error if you are not in a
> >>transaction, so it would fill the logs with errors.
> >>    
> >>
> >
> >Won't that break when we have nested transactions implemented?  i.e. 
> >begin;commit; would just open a sub transaction and have no effect on the 
> >outer transaction...
> >  
> >
> I was just about to mention that one.  Perhaps a ROLLBACK ALL would be
> of benefit to allow a clean state and start to work again.
> 
> Doesn't autocommit behavior affect this as well?

No, autocommit is now in the clients, but even if it was in the server,
BEGIN;COMMIT would be OK.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Andreas Pflug
Date:
Subject: initdb fails: problem with array?
Next
From: Bruno Wolff III
Date:
Subject: Re: suggestions to improve postgresql suitability for data-mining