Re: pgbench - allow to store select results intovariables

Поиск
Список
Период
Сортировка
От Tatsuo Ishii
Тема Re: pgbench - allow to store select results intovariables
Дата
Msg-id 20170405.094548.1184280384967203518.t-ishii@sraoss.co.jp
обсуждение исходный текст
Ответ на Re: pgbench - allow to store select results into variables  (Rafia Sabih <rafia.sabih@enterprisedb.com>)
Ответы Re: pgbench - allow to store select results intovariables
Список pgsql-hackers
>> Please find attached a v8 which hopefully fixes these two issues.
> Looks good to me, marking as ready for committer.

I have looked into this a little bit.

It seems the new feature \gset doesn't work with tables having none
ascii column names:

$ src/bin/pgbench/pgbench -t 1 -f /tmp/f test
starting vacuum...end.
gset: invalid variable name: "数字"
client 0 file 0 command 0 compound 0: error storing into var 数字
transaction type: /tmp/f
scaling factor: 1
query mode: simple
number of clients: 1
number of threads: 1
number of transactions per client: 1
number of transactions actually processed: 0/1

This is because pgbench variable names are limited to ascii
ranges. IMO the limitation is unnecessary and should be removed. (I
know that the limitation was brought in by someone long time ago and
the patch author is not responsible for that).

Anyway, now that the feature reveals the undocumented limitation, we
should document the limitation of \gset at least.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [PATCH] Reduce src/test/recovery verbosity
Следующее
От: Tatsuo Ishii
Дата:
Сообщение: Re: Statement timeout behavior in extended queries