Re: php with postgres

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Marcus Brger <marcus(dot)boerger(at)post(dot)rwth-aachen(dot)de>
Cc: Jan Wieck <JanWieck(at)Yahoo(dot)com>, ivan <iv(at)psycho(dot)pl>, Joe Conway <mail(at)joeconway(dot)com>, Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: php with postgres
Date: 2003-07-23 04:18:13
Message-ID: 200307230418.h6N4ID526477@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marcus B?rger wrote:
> >> However it may be very usefull to terminate any open transaction before
> >> reusing a persisten connection. Typically this happens when the same script
> >> runs again. But anyway using transactions together with persistent conenctions
> >> in a multithreaded environment isn't the best thing you could do. So our
> >> options are
> >> 1) tell the users to do 'auto commit mode'
> >> 2) nested transactions
> >> 3) locking
> >>
> >> >From my perspective 2) and 3) are bad ideas for the web environment. In other
> >> words i guess we should leave it as is with transaction rollback only when the
> >> client terminates (e.g. the webserver stops).
>
> BM> I don't see why you wouldn't just do BEGIN;COMMIT;RESET ALL; when you
> BM> pass the connection to a new client.
>
>
> Bruce you said RESET ALL is available since 7.2. I am currently checking for
> the lib version but it would be more correct to check something on the server.
> So the question what do i check?

We usually use SELECT version().

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-07-23 04:19:45 Re: php with postgres
Previous Message Oleg Bartunov 2003-07-23 04:16:52 Re: tsearch2 for 7.3.X