Feedback-ID: i76984098:Fastmail
Message-ID: <c3083a64-c495-4fa6-80cc-67f0e316f042@aklaver.com>
Date: Mon, 10 Jun 2024 13:13:43 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: libpq v17 PQsocketPoll timeout is not granular enough
To: Dominique Devienne <ddevienne@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@postgresql.org
References: <CAFCRh-8hf=7V8UoF63aLxSkeFmXX8-1O5tRxHL61Pngb7V9rcw@mail.gmail.com>
 <740207.1718036299@sss.pgh.pa.us>
 <CAFCRh-8zngmAsYfLyrmz6mDhPPF5uh8YRBCcMJjdUidKBeFSxw@mail.gmail.com>
Content-Language: en-US
From: Adrian Klaver <adrian.klaver@aklaver.com>
In-Reply-To: <CAFCRh-8zngmAsYfLyrmz6mDhPPF5uh8YRBCcMJjdUidKBeFSxw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/c3083a64-c495-4fa6-80cc-67f0e316f042%40aklaver.com>
Precedence: bulk

On 6/10/24 11:43, Dominique Devienne wrote:
> Bummer… I didn’t presume to suggest an api before, but simply adding an 
> extra int with the milliseconds offset from the time_t is simple, and 
> trivial to plug into the implementation I saw. Callers who don’t care 
> can simply pass zero. while I could pass a computed time_t and ms offset 
> using <chrono>. No need for fancy types imho. Aren’t betas precisely for 

https://www.postgresql.org/developer/beta/

"PostgreSQL beta and release candidate releases are pre-release testing 
versions before the community makes a new release generally available. 
They are feature-frozen (i.e. no new features are added), and we release 
these to the public for testing before our final release. PostgreSQL 
beta and release candidate release are not meant for use in production 
systems."


> the purpose of exposing apis to those like myself to vet them? This is 
> also beta1, I,e, the first one. My €0.02
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com