| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| 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:08:14 |
| Message-ID: | CA+TgmoYEXMHWRXV8gaUHiSzjugLv6ovUGd1Gj0RF5t0C6npx-w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 12, 2024 at 3:00 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Hmm ... pg_int64 is the only such typedef I'm seeing in that file.
I grepped the whole directory for '^} '.
> But okay, it's a precedent. The thing I'm having difficulty with
> is that I'd like the typedef name to allude to time_t, and I don't
> think fooling with the casing of that will be helpful in making
> the allusion stick. 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.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2024-06-12 19:10:29 | Re: Addressing SECURITY DEFINER Function Vulnerabilities in PostgreSQL Extensions |
| Previous Message | Robert Haas | 2024-06-12 19:07:16 | Re: RFC: adding pytest as a supported test framework |