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 06:34:53 |
Message-ID: | alpine.DEB.2.20.1704171524050.4025@lancre |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello Tatsuo-san,
> Thank you for the patch. I tested a little bit and found that it does
> not allow value replacement against non ascii variables in given SQL
> statements . Is it intentional?
No, this is a bug.
> If not, I think you need to fix parseVariable() as well.
Indeed. Here is v2.
--
Fabien.
Attachment | Content-Type | Size |
---|---|---|
pgbench-utf8-vars-2.patch | text/x-diff | 3.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2017-04-17 06:40:31 | Re: pgbench - allow to store select results into variables |
Previous Message | Fabien COELHO | 2017-04-17 06:09:23 | Re: Variable substitution in psql backtick expansion |