From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgbench post-connection command |
Date: | 2012-01-12 15:51:56 |
Message-ID: | 4F0F019C.1070701@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12.01.2012 17:26, Tom Lane wrote:
> Simon Riggs<simon(at)2ndQuadrant(dot)com> writes:
>> New -x option for pgbench executes the given command once after
>> connection of each session.
If it's just for SET, you could just put the GUCs in postgresql.conf.
> This seems rather poorly designed, mainly because there's no reason to
> think that a single command would be sufficient.
>
> What would make more sense to me is to add an option for a one-time
> script, or possibly extend the script language to allow marking some
> commands as "do once".
Hmm, that might be handy. I wanted to write a some tests a while ago
where each session operated on a separate table. With this, I could've
put the CREATE TABLE statement in the statup-script.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Satoshi Nagayasu | 2012-01-12 15:58:57 | Re: log messages for archive recovery progress |
Previous Message | Andrew Dunstan | 2012-01-12 15:51:13 | Re: JSON for PG 9.2 |