Skip site navigation (1) Skip section navigation (2)

Re: pgbench post-connection command

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pgbench post-connection command
Date: 2012-01-13 09:34:05
Message-ID: CA+U5nMK1p7kDsKXiF++d5soub8assOyNJCXe_qf_L=hQQmxehw@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Thu, Jan 12, 2012 at 8:04 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
>> On Thu, Jan 12, 2012 at 5:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Pierre CDate: 2012-01-13 09:48:56
Subject: Re: Inlining comparators as a performance optimisation
Previous:From: Simon RiggsDate: 2012-01-13 09:17:37
Subject: Re: ERRCODE_READ_ONLY_SQL_TRANSACTION

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group