public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dominique Devienne <[email protected]>
To: [email protected]
Subject: Re: Using PQsocketPoll() for PIPELINE mode
Date: Tue, 27 Aug 2024 12:23:52 +0200
Message-ID: <CAFCRh--frt-aqnMo2F619FK6sU=3RJkxFRoQ8P8i5mdieQtpOQ@mail.gmail.com> (raw)
In-Reply-To: <CAFCRh-9R91Huzk2KFS8iKEo_eSXaZ0iAkGwx6LxfUexKzkeeRA@mail.gmail.com>
References: <CAFCRh-9R91Huzk2KFS8iKEo_eSXaZ0iAkGwx6LxfUexKzkeeRA@mail.gmail.com>

On Wed, Aug 14, 2024 at 2:50 PM Dominique Devienne <[email protected]> wrote:
> Hi. I've now used successfully the new PQsocketPoll() API
> in the context of waiting for notifications, using beta2 and 3.
>
> But now I'm looking into using it in the context of PIPELINE mode.
> Where I suppose both forRead and forWrite are 1, but the return
> code only indicates whether the condition is met. The doc says nothing
> about OR or AND semantic, when both forRead and forWrite are true.
>
> Perhaps it's deemed obvious from the use of select() or poll()?
> Or is one supposed to call it once with forRead=forWrite=1 and
> a timeout, then call it again twice with just one forFlag set and
> a 0 timeout, to know the "details" about which "side" is ready?
>
> Or hasn't this use case been considered for PQsocketPoll(),
> and thus the current return code isn't has precise as it could be?
>
> Thanks for any precisions, --DD

Hi. No answers. Was it wrong timing (vacations) or
is something wrong with my questions? Thanks, --DD

view thread (2+ messages)  latest in thread

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]
  Subject: Re: Using PQsocketPoll() for PIPELINE mode
  In-Reply-To: <CAFCRh--frt-aqnMo2F619FK6sU=3RJkxFRoQ8P8i5mdieQtpOQ@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