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

From Simon Riggs
Subject Re: pgbench post-connection command
Date
Msg-id CA+U5nMK1p7kDsKXiF++d5soub8assOyNJCXe_qf_L=hQQmxehw@mail.gmail.com
Whole thread Raw
In response to Re: pgbench post-connection command  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pgbench post-connection command  (Greg Smith <greg@2ndQuadrant.com>)
List pgsql-hackers
On Thu, Jan 12, 2012 at 8:04 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndQuadrant.com> writes:
>> On Thu, Jan 12, 2012 at 5:32 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> More like "\once ... any SQL command or meta command here ..."
>>> if we want to extend the scripting language.  But I'd be perfectly happy
>>> with a command-line switch that specifies a script file to be run once.
>
>> Once per connection, yes?
>
> Hmmm ... good question.  Heikki was speculating about doing CREATE TABLE
> or similar, which you'd want done only once period.  But I see no very
> strong reason why cases like that couldn't be handled outside of
> pgbench.  So yeah, once per connection.

OK, its a TODO item, but I don't think I'll have time for it for the next CF.

If we need it during testing of other patches then I'll write it.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: ERRCODE_READ_ONLY_SQL_TRANSACTION
Next
From: "Pierre C"
Date:
Subject: Re: Inlining comparators as a performance optimisation