Simon Riggs <si...@2ndquadrant.com> writes:
> On Thu, Jan 12, 2012 at 3:26 PM, Tom Lane <t...@sss.pgh.pa.us> wrote:
>> This seems rather poorly designed, mainly because there's no reason to
>> think that a single command would be sufficient.
> It supports multiple commands via multi-statement requests
> e.g.
> -x "SET this = on; SET that = off"
I don't believe that works for multiple \set commands, which is the
more likely use-case for this; as noted upthread, executing SET here
is quite unnecessary since you can get that behavior with
"export PGOPTIONS".
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
