| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, Robert Haas <robertmhaas(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgbench - allow to store select results into variables |
| Date: | 2017-01-05 09:47:43 |
| Message-ID: | alpine.DEB.2.20.1701051033260.3661@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Tom,
> Please look at changing \into to be a SQL-command-ending backslash
> command as we previously discussed.
Hmmm.
I do want storing results & compound command ending to be orthogonal.
In order to keep this feature, I think that I can move the
"into/ginto/gset/..." at the end of the command. For the compound command
list to necessarily end, I can probably do some reassembly as a post phase
on Commands in pgbench so that the impact on the lexer is much reduced, in
particular without undue "hackery" as you put it.
--
Fabien.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2017-01-05 09:59:26 | Re: proposal: session server side variables |
| Previous Message | Etsuro Fujita | 2017-01-05 09:19:51 | Re: postgres_fdw : altering foreign table not invalidating prepare statement execution plan. |