Re: pgbench post-connection command
От | Simon Riggs |
---|---|
Тема | Re: pgbench post-connection command |
Дата | |
Msg-id | CA+U5nM+pg2eGyBwxaFm4bn1KTDSn566-e8fWkOEPb9OBZ0_Diw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgbench post-connection command (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pgbench post-connection command
|
Список | pgsql-hackers |
On Thu, Jan 12, 2012 at 4:24 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > 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". OK, so you want... \setonce <command> or? -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: