| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgbench - allow to store select results into variables |
| Date: | 2017-04-08 20:37:07 |
| Message-ID: | alpine.DEB.2.20.1704090534460.26549@lancre |
| Views: | Whole Thread | Raw Message | 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 should be asleep:-(
Wrong patch suffix, wrong from, multiple apology:-(
Here it is again.
--
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 | Robert Haas | 2017-04-08 21:01:06 | Re: [sqlsmith] Planner crash on foreign table join |
| Previous Message | Fabien COELHO | 2017-04-08 20:32:17 | Re: pgbench - allow to store select results into variables |