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. -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
