Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sQwoj-00CTX8-CW for pgsql-general@arkaria.postgresql.org; Mon, 08 Jul 2024 22:26:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sQwoh-00A7f5-Qu for pgsql-general@arkaria.postgresql.org; Mon, 08 Jul 2024 22:26:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sQwoh-00A7ew-Es for pgsql-general@lists.postgresql.org; Mon, 08 Jul 2024 22:26:39 +0000 Received: from mail-oa1-x33.google.com ([2001:4860:4864:20::33]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sQwoe-0016RD-BK for pgsql-general@postgresql.org; Mon, 08 Jul 2024 22:26:37 +0000 Received: by mail-oa1-x33.google.com with SMTP id 586e51a60fabf-24c9f630e51so2789850fac.1 for ; Mon, 08 Jul 2024 15:26:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=datadoghq.com; s=google; t=1720477595; x=1721082395; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=OPAEnVfLg4V09+3gfxBSpqFZY+e9/KHElCVaYm7ZALo=; b=O1Kpb96FaoKOG42zZXqA8/PFJBUtKqfu2a9EJVMvnmVUmxnqHk85qcy2Qmt4ItRrQv q0x1j6aYGCBZ1lSap1BPC0nfoQdmgp2NHipDMzZsTltSN0r5s3wpzAtES/dNSk81B8lV JUhyHE70iA3Vqm3OptzjR6aaZsg4Y7zR7ZfOc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1720477595; x=1721082395; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=OPAEnVfLg4V09+3gfxBSpqFZY+e9/KHElCVaYm7ZALo=; b=WqqzDXa86MrZ10Qz27o4GmTlc0uJwEUwOFIHwxgPM9Xepx2snkcr96DGk8bJSYXT4l iooXW6UhtF1lT7rqZVpyFVJ2Y05+Zzur3YVUAm7iUFkPZOctBLtJRBMY8JJLG8LDWzVW bmGst/63ShXS8748JjSt1ClQUaCgDZz9smXx70LQ1sZ/CAiOCotdzum6bNRQZjC2C/R0 j/bPi3u4IxEAm9kDaOKnNLzX4E/gtN9QddbDC3fCEaJc8Uc043dZCHmvyHXRKsgkg4Ot wy1T7kDQdK+tj8qYyZNlaBNFlhWzXdPesY7WKvXPhXCbw+8QieDuRo7an/+2iqJPyPP1 16ZA== X-Gm-Message-State: AOJu0YyO4FT7qHqDUzyN5wjRbpA8s3w/NrHOlEjtw1Tenrfw8T+X0m1m lzOQkpS6PP2n569TJlP4kcrIV3IWZvdxrAJCBxrn0NfDyBVnKSpOXl0udpgP0Fg5DEKS+YR5ZnR aV6Ahr/M9WnZjEFoxL8lUt2lidvXw/+URG/eWEm+pqaLLtsOcQn8= X-Google-Smtp-Source: AGHT+IHHRec25T2NsWQyUpBCk7rjHwmtb5RjlJuhfgLjdzsZMDbxBoMCzgA2MfrOF0gZtUx4bPi4sV02yMqE7gkTODk= X-Received: by 2002:a05:6870:ac26:b0:23c:bc3a:6ccb with SMTP id 586e51a60fabf-25eae7baa68mr608694fac.19.1720477595035; Mon, 08 Jul 2024 15:26:35 -0700 (PDT) MIME-Version: 1.0 From: Joseph Hammerman Date: Mon, 8 Jul 2024 15:26:23 -0700 Message-ID: Subject: SQL: Chaining versus Pipelining To: pgsql-general@postgresql.org Content-Type: multipart/alternative; boundary="000000000000e5ecf2061cc3e71c" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e5ecf2061cc3e71c Content-Type: text/plain; charset="UTF-8" Hi PgSQL general mailing lists, 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? Thanks in advance for any assistance anyone can provide, Joseph Hammerman --000000000000e5ecf2061cc3e71c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi PgSQL general mailing=C2=A0lists,

In= Postgres Weekly, I encountered this interesti= ng article. The documentation on the use of AND CHAIN is here. A co-= worker is interested in the difference between=C2=A0chaining and using the = pipelining=C2=A0syntax.

They look pretty sim= ilar 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?
<= div>
Thanks in advance for any assistance anyone can provide,=
Joseph Hammerman
--000000000000e5ecf2061cc3e71c--