Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Why exactly did you want the initial SET to not be part of the
> transaction?
Primarily because existing client-side libraries issue lots of SETs
while starting a connection.
We may just have to say "those guys are broken if you turn off
autocommit in postgresql.conf", but I am looking for a way around it.
If SET didn't start a transaction then they wouldn't be broken...
regards, tom lane