| From: | Fabien COELHO <fabien(dot)coelho(at)mines-paristech(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-08 20:32:17 |
| Message-ID: | alpine.DEB.2.20.1704090529570.26549@lancre |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> As the variable infrastructures are pretty different between psql & pgbench
> (typed vs untyped values, sorted array vs linked list data structure, no hook
> vs 2 hooks, name spaces vs no such thing...), I have chosen the simplest
> option of just copying the name checking function and extending the lexer to
> authorize non-ascii letters, so that psql/pgbench would accept the same
> variable names with the same constraint about encodings.
>
> See patch attached & test script.
Argh, I'm jet-lagged, wrong patch suffix... Here it is with the right
suffix.
--
Fabien.
| Attachment | Content-Type | Size |
|---|---|---|
| pgbench-utf8-vars-1.patch | text/x-diff | 2.8 KB |
| pgbench-utf8-vars.sql | application/x-sql | 101 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2017-04-08 20:37:07 | Re: pgbench - allow to store select results into variables |
| Previous Message | Andrew Gierth | 2017-04-08 20:27:28 | Re: [sqlsmith] Planner crash on foreign table join |