Re: php with postgres

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Marcus Börger <marcus(dot)boerger(at)post(dot)rwth-aachen(dot)de>, 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-22 01:16:25
Message-ID: 3F1C9069.6040206@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian wrote:
> Marcus B?rger wrote:
>> BM> Marcus, would you check if PHP is using RESET ALL when passing
>> BM> persistent connection to new clients? We added that capability a few
>> BM> releases ago, specifically for PHP persistent connections, but I don't
>> BM> think that ever got into the PHP code.
>>
>> Unfortunately we don't do so yet. Do i need to check for errors or can i do it
>> unconditionally on conenction start? And i'd need to know how to check if it
>> is available (like starting with which version).
>
> It first appeared in PostgreSQL version 7.2. It doesn't generate any
> failures. It just resets all SET settting to their defaults, in case
> the previous client modified them.
>

It does generate the usual error if the current transaction block is in
ABORT state. So the correct querystring to send would be something like

"ROLLBACK; RESET ALL"

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2003-07-22 01:20:27 Re: php with postgres
Previous Message Bruce Momjian 2003-07-22 01:09:59 Re: SELECT FOR UPDATE NOWAIT