Re: [HACKERS] pgbench - allow to store select results intovariables

Поиск
Список
Период
Сортировка
От Fabien COELHO
Тема Re: [HACKERS] pgbench - allow to store select results intovariables
Дата
Msg-id alpine.DEB.2.21.1811241751070.12627@lancre
обсуждение исходный текст
Ответ на Re: [HACKERS] pgbench - allow to store select results into variables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Ответы Re: [HACKERS] pgbench - allow to store select results into variables  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
Дерево обсуждения 
> FWIW I think the terminology in this patch is wrong.  You use the term
> "compound" to mean "one query within a string containing multiple
> queries", but that's not what compound means.  Compound is the whole
> thing, comprised of the multiple queries.

Indeed. Compounded query?

> Maybe "query" is the right word to use there, not sure.

I do not understand, "query queries"?

I think it should avoid using sql-related words, such as "group", 
"aggregate", "merge", "join"...

I thought of "combined", meaning the queries are combined together in a 
single message at the protocol level.

Basically I'm ok with any better idea.

-- 
Fabien.

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

Предыдущее
От: Jeff Janes
Дата:
Сообщение: Don't wake up to check trigger file if none is configured
Следующее
От: Fabien COELHO
Дата:
Сообщение: Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" testpending solution of its timing is (fwd)