Re: pgbench - allow to store select results into variables
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: coelho@cri.ensmp.fr, rafia.sabih@enterprisedb.com,
michael.paquier@gmail.com, Langote_Amit_f8@lab.ntt.co.jp,
robertmhaas@gmail.com, pavel.stehule@gmail.com,
pgsql-hackers@postgresql.org
Date: 2017-09-04T17:46:52Z
Lists: pgsql-hackers
Tatsuo Ishii <ishii@sraoss.co.jp> writes: >> Here is a v3 with a more precise comment. > Looks good to me. I have marked the patch status as "Ready for > committer". LGTM too. Pushed with a minor adjustment to make parseVariable() have exactly the same test as valid_variable_name(). regards, tom lane
Commits
-
pgbench: Remove \cset
- 25ee70511ec2 12.0 landed
-
pgbench: add \cset and \gset commands
- 6260cc550b0e 12.0 landed
-
Adjust pgbench to allow non-ASCII characters in variable names.
- 9d36a386608d 11.0 landed
-
Refactor script execution state machine in pgbench.
- 12788ae49e19 10.0 cited
-
Allow empty queries in pgbench.
- 6471045230f5 10.0 cited