| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| 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 16:10:32 |
| Message-ID: | 22002.1326384632@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
> 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.
Or use PGOPTIONS. I think there might be a use-case for this sort of
thing, but it's going to be more complicated than a SET or two; that's
why I think the feature ought to provide for a script not just a
command.
One particular use-case that comes to mind is executing \set commands
that only need to be done once, not once per iteration.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2012-01-12 16:12:09 | Re: pgbench post-connection command |
| Previous Message | Tom Lane | 2012-01-12 16:06:10 | Re: Remembering bug #6123 |