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: tgl(at)sss(dot)pgh(dot)pa(dot)us, rafia(dot)sabih(at)enterprisedb(dot)com, michael(dot)paquier(at)gmail(dot)com, 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-17 11:00:07
Message-ID: alpine.DEB.2.20.1704171959080.1741@lancre
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


> I think you'd better to change the following comments because there's
> no psqlscan.l or psqlscanslash.l in pgbench source tree.
> + * underscore. Keep this in sync with the definition of variable_char in
> + * psqlscan.l and psqlscanslash.l.

Here is a v3 with a more precise comment.


Attachment Content-Type Size
pgbench-utf8-vars-3.patch text/x-diff 3.2 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Remi Colinet 2017-04-17 12:09:01 [PATCH] New command to monitor progression of long running queries
Previous Message Kyotaro HORIGUCHI 2017-04-17 10:39:55 Re: some review comments on logical rep code