Re: [HACKERS] pgbench - allow to store select results intovariables - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] pgbench - allow to store select results intovariables
Date
Msg-id alpine.DEB.2.20.1704090529570.26549@lancre
Whole thread Raw
In response to Re: [HACKERS] pgbench - allow to store select results intovariables  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: [HACKERS] pgbench - allow to store select results intovariables  (Tatsuo Ishii <ishii@sraoss.co.jp>)
List 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.
-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: [HACKERS] [sqlsmith] Planner crash on foreign table join
Next
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] pgbench - allow to store select results intovariables