| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vik Fearing <vik(at)postgresfriends(dot)org> |
| 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:37:15 |
| Message-ID: | 603162.1751935035@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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. Also, AFAICS there's no way to stuff nanosecond
precision and a reasonable timestamp range (at least a few thousand
years IMO) into 64 bits, so the compatibility break would include
expending more disk space. Hard to believe that it's worth it.
(If we did decide to break compatibility, my own first priority
would be to make timestamptz actually include a timezone ...)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2025-07-08 00:46:17 | Re: What is a typical precision of gettimeofday()? |
| Previous Message | Michael Paquier | 2025-07-08 00:36:53 | Re: Adding wait events statistics |