public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jelte Fennema-Nio <[email protected]>
To: Michael Paquier <[email protected]>
Cc: Anthonin Bonnefoy <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Add Pipelining support in psql
Date: Thu, 28 Nov 2024 10:06:28 +0100
Message-ID: <CAGECzQTiCvOxxuA98Ei+qVb1px82eP-iRvJvnvrcKU1de55-Pw@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAO6_XqroE7JuMEm1sWz55rp9fAYX2JwmcP_3m_v51vnOFdsLiQ@mail.gmail.com>
<CAGECzQTjCEXpJGOq9O6Nf+p4zRwjt-b1p6kACWVNJ+uYcLGvyg@mail.gmail.com>
<[email protected]>
On Thu, 28 Nov 2024 at 07:43, Michael Paquier <[email protected]> wrote:
> Hmm. The start, end and sync meta-commands are useful for testing. I
> find the flush control a bit less interesting, TBH.
>
> What would you use these for?
I guess mostly for interactively playing around with pipelining from psql.
But I think \getresult would be useful for testing too. This would
allow us to test that we can read part of the pipeline, without
sending a sync and waiting for everything.
To be clear \flushrequest and \flush would be necessary to make
\getresult work reliably.
view thread (3+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Add Pipelining support in psql
In-Reply-To: <CAGECzQTiCvOxxuA98Ei+qVb1px82eP-iRvJvnvrcKU1de55-Pw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox