Re: Lost search_path after transaction fails - Mailing list pgsql-bugs

From David Newall
Subject Re: Lost search_path after transaction fails
Date
Msg-id 4998AFEC.3000706@davidnewall.com
Whole thread Raw
In response to Re: Lost search_path after transaction fails  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-bugs
Heikki Linnakangas wrote:
> ecpg implicitly runs everything inside transactions. You don't need to
> run START TRANSACTION, that's implicit. Therefore the "set
> search_path" command is in fact run in the same transaction as the
> failing insert, as also hinted by the warning "there is already a
> transaction in progress" at the START TRANSACTION command.

Thanks for your reply.  Committing after setting search_path does
resolve this problem.  It surprises me that a session parameter is
treated in this way.

pgsql-bugs by date:

Previous
From: "Fujii Masao"
Date:
Subject: BUG #4657: mod() makes a mistake in calculation in v8.3
Next
From: "Mathias Seiler"
Date:
Subject: BUG #4656: Indexes not used when comparing nextval() and currval() to integers