| From: | "Daniel Verite" <daniel(at)manitou-mail(dot)org> |
|---|---|
| To: | "Fabien COELHO" <coelho(at)cri(dot)ensmp(dot)fr> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pgsql: Add libpq pipeline mode support to pgbench |
| Date: | 2021-03-17 13:24:55 |
| Message-ID: | 57c58502-f053-4058-81cb-840e6504b0a9@manitou-mail.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Fabien COELHO wrote:
> For consistency with the existing \if … \endif, ISTM that it could have
> been named \batch … \endbatch or \pipeline … \endpipeline?
"start" mirrors "end". To me, the analogy with \if-\endif is not
obvious.
Grammatically \if is meant to introduce the expression after it,
whereas \startpipeline takes no argument.
Functionally \startpipeline can be thought as "open the valve"
and \endpipeline "close the valve". They're "call-to-action" kinds of
commands, and in that sense quite different from the \if-\endif pair.
Best regards,
--
Daniel Vérité
PostgreSQL-powered mailer: https://www.manitou-mail.org
Twitter: @DanielVerite
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-03-17 17:09:19 | pgsql: Doc: improve discussion of variable substitution in PL/pgSQL. |
| Previous Message | Thomas Munro | 2021-03-17 12:17:29 | pgsql: Revert "Fix race in Parallel Hash Join batch cleanup." |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Surafel Temesgen | 2021-03-17 13:53:46 | Re: Calendar support in localization |
| Previous Message | torikoshia | 2021-03-17 13:24:27 | Re: Get memory contexts of an arbitrary backend process |