Re: Issues with EPOCH-s, TIMESTAMP(TZ)-s and leap seconds.

From: Nem Tudom <ellenallhatatlan(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Issues with EPOCH-s, TIMESTAMP(TZ)-s and leap seconds.
Date: 2025-01-28 14:00:20
Message-ID: 5a4de43a-22ef-4b35-9ea4-57a5b2f520c6@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 28/01/2025 00:05, Thomas Munro wrote:

Thanks to you and all the others who took the trouble to reply,

> I showed the bones of how you could do this in SQL here:
> https://www.postgresql.org/message-id/CA%2BhUKGLU9Don4YHnfdzn0eeWQsUu8GJDaLiUAefLLT6%3DmmeGoQ%40mail.gmail.com

The technical explanation is much appreciated - I'd gathered (more or
less) as much from my searching and reading the leap second Wiki.

So, the situation is that, basically, leap seconds are "fudged" to use
the technical term!

I asked the question with a view to having accurate TIMESTAMP
differences - i.e. to the second. However, since everyone is fudging
(incl. AFAICS Oracle and SQL Server), this means that accepting the
status quo will just make my inaccuracies will be the same as everyone
else's, ergo I'm golden!

At least that's one issue that I can safely ignore - I didn't fancy
implementing this on my own.

Thanks again and rgs,

E!

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2025-01-28 14:20:59 Re: Log retention query
Previous Message Paul Brindusa 2025-01-28 13:40:42 Re: Log retention query