Re: pgbench - allow to store select results into variables

Fabien COELHO <coelho@cri.ensmp.fr>

From: Fabien COELHO <coelho@cri.ensmp.fr>

To: Tatsuo Ishii <ishii@sraoss.co.jp>

Cc: rafia.sabih@enterprisedb.com, michael.paquier@gmail.com, tgl@sss.pgh.pa.us, Langote_Amit_f8@lab.ntt.co.jp, robertmhaas@gmail.com, pavel.stehule@gmail.com, PostgreSQL Developers <pgsql-hackers@postgresql.org>

Date: 2017-04-05T18:28:46Z

Lists: pgsql-hackers

Attachments

pgbench-into-9.patch (text/x-diff) patch

Hello Tatsuo-san,

> It seems the new feature \gset doesn't work with tables having none
> ascii column names:

Indeed. The same error is triggered with the \set syntax, which does not 
involve any query execution.

I have added a sentence mentionning the restriction when variables are 
first discussed in the documentation, see attached patch.

-- 
Fabien.

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