|From:||Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>|
|To:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|Cc:||Michael Paquier <michael(at)paquier(dot)xyz>, Stephen Frost <sfrost(at)snowman(dot)net>, Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, PostgreSQL Developers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: [HACKERS] pgbench - allow to store select results into variables|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
> 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.
|Next Message||Fabien COELHO||2018-11-24 16:58:38||Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" test pending solution of its timing is (fwd)|
|Previous Message||Jeff Janes||2018-11-24 16:29:22||Don't wake up to check trigger file if none is configured|