Re: pgbench - allow to store select results into variables

From: Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>
To: Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp>
Cc: rafia(dot)sabih(at)enterprisedb(dot)com, michael(dot)paquier(at)gmail(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us, Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp, robertmhaas(at)gmail(dot)com, 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-04-05 18:28:46
Message-ID: alpine.DEB.2.20.1704052019100.1967@lancre
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers


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.

Attachment Content-Type Size
pgbench-into-9.patch text/x-diff 16.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavan Deolasee 2017-04-05 18:32:41 Re: Patch: Write Amplification Reduction Method (WARM)
Previous Message Andres Freund 2017-04-05 18:27:30 Re: Patch: Write Amplification Reduction Method (WARM)