| From: | Joseph Hammerman <joe(dot)hammerman(at)datadoghq(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | SQL: Chaining versus Pipelining |
| Date: | 2024-07-08 22:26:23 |
| Message-ID: | CAHs7QM8VJ1pAYR7zdJ9GwbXhVbJEUnLw+sM=bMNNrXFMvaji8g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi PgSQL general mailing lists,
In Postgres Weekly, I encountered this
<https://bugfactory.io/articles/using-transaction-chaining-to-reduce-server-round-trips/>
interesting article. The documentation
<https://www.postgresql.org/docs/current/plpgsql-transactions.html> on the
use of AND CHAIN is here. A co-worker is interested in the difference
between chaining and using the pipelining
<https://www.postgresql.org/docs/current/libpq-pipeline-mode.html> syntax.
They look pretty similar to me; it could be that one implementation is PG
specific and not part of the SQL standard or something. Can anyone shed any
light for us?
Thanks in advance for any assistance anyone can provide,
Joseph Hammerman
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-07-08 22:39:11 | Re: v16 roles, SET FALSE, INHERIT FALSE, ADMIN FALSE |
| Previous Message | Tom Lane | 2024-07-08 22:08:50 | Re: v16 roles, SET FALSE, INHERIT FALSE, ADMIN FALSE |