Re: pgbench post-connection command - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pgbench post-connection command
Date
Msg-id 22319.1326385466@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgbench post-connection command  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: pgbench post-connection command  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On Thu, Jan 12, 2012 at 3:26 PM, Tom Lane <tgl@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


pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: JSON for PG 9.2
Next
From: Pavel Stehule
Date:
Subject: Re: JSON for PG 9.2