Re: libpq v17 PQsocketPoll timeout is not granular enough - Mailing list pgsql-general

From Adrian Klaver
Subject Re: libpq v17 PQsocketPoll timeout is not granular enough
Date
Msg-id c3083a64-c495-4fa6-80cc-67f0e316f042@aklaver.com
Whole thread Raw
In response to Re: libpq v17 PQsocketPoll timeout is not granular enough  (Dominique Devienne <ddevienne@gmail.com>)
List pgsql-general
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




pgsql-general by date:

Previous
From: Rich Shepard
Date:
Subject: Re: Multiple tables row insertions from single psql input file
Next
From: Adrian Klaver
Date:
Subject: Re: Does trigger only accept functions?