Re: SQL: Chaining versus Pipelining

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Joseph Hammerman <joe(dot)hammerman(at)datadoghq(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: SQL: Chaining versus Pipelining
Date: 2024-07-09 07:48:24
Message-ID: 226de12aadd5b3a5186c9ae087e7a609bd3a5769.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, 2024-07-08 at 15:26 -0700, Joseph Hammerman wrote:
> In Postgres Weekly, I encountered this interesting article. The documentation on the use
> of AND CHAIN is here. A co-worker is interested in the difference between chaining
> and using the pipelining 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?

COMMIT AND CHAIN and pipelining have little in common, except that they can both
reduce the overhead caused by a high latency between database client and server.

COMMIT AND CHAIN just saves you a round trip.

Pipelining allows you to send the next database request before you get the response
to the first one.

Here is an article that describes pipelining:
https://www.cybertec-postgresql.com/en/pipeline-mode-better-performance-on-slow-network/

Yours,
Laurenz Albe

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Shenavai, Manuel 2024-07-09 11:38:40 autovacuum_vacuum_cost_delay
Previous Message Laurenz Albe 2024-07-09 07:42:51 Re: Logical Replication - PG_Wall size is too big, What can I do ?