From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Tristan Partin <tristan(at)partin(dot)io>, Dominique Devienne <ddevienne(at)gmail(dot)com> |
Subject: | Re: Improve the granularity of PQsocketPoll's timeout parameter? |
Date: | 2024-06-12 19:29:40 |
Message-ID: | 1521054.1718220580@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Jun 12, 2024 at 3:00 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So how about one of
>> pg_usec_time_t
>> pg_time_t_usec
>> ?
> The former seems better to me, since having _t not at the end does not
> seem too intuitive.
True. We can guess about how POSIX might spell this if they ever
invent the concept, but one choice they certainly would not make
is time_t_usec.
v3 attached uses pg_usec_time_t, and fixes one brown-paper-bag
bug the cfbot noticed in v2.
regards, tom lane
Attachment | Content-Type | Size |
---|---|---|
pqsocketpoll-in-microseconds-v3.patch | text/x-diff | 13.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Jacob Champion | 2024-06-12 19:30:53 | Re: RFC: adding pytest as a supported test framework |
Previous Message | Robert Haas | 2024-06-12 19:11:53 | Re: On disable_cost |