From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, hannuk(at)google(dot)com, x4mmm(at)yandex-team(dot)ru |
Subject: | Re: What is a typical precision of gettimeofday()? |
Date: | 2025-07-08 00:46:17 |
Message-ID: | 39903bd6-6e51-46f4-95c0-49284f45529b@postgresfriends.org |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08/07/2025 02:37, Tom Lane wrote:
> Vik Fearing <vik(at)postgresfriends(dot)org> writes:
>> Having read through this thread, is there any chance at all that we
>> might be able to implement feature F555, “Enhanced seconds precision”?
> Don't see how we could do that without an on-disk compatibility break
> for timestamps.
Yeah, I don't see how either.
> (If we did decide to break compatibility, my own first priority
> would be to make timestamptz actually include a timezone ...)
That comes with its own set of issues, but I don't want to hijack this
thread more than I already have.
--
Vik Fearing
From | Date | Subject | |
---|---|---|---|
Next Message | Tender Wang | 2025-07-08 00:52:13 | Re: MergeJoin beats HashJoin in the case of multiple hash clauses |
Previous Message | Tom Lane | 2025-07-08 00:37:15 | Re: What is a typical precision of gettimeofday()? |