From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Nem Tudom <ellenallhatatlan(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-27 21:47:04 |
Message-ID: | e45294c1-3448-463a-8985-74894f811f94@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 1/27/25 13:23, Nem Tudom wrote:
Reply to list also.
Ccing list.
See post from Peter Holzer .
>
>
> Hi Adrian, all,
>
>
>>> Any help, advice, recommendations, URL-s, references &c. appreciated.
>
>> https://www.postgresql.org/docs/current/functions-datetime.html
>> https://www.postgresql.org/docs/current/view-pg-timezone-names.html
>
>> " (Technically, PostgreSQL does not use UTC because leap seconds are
>> not handled.)"
>
> Well, that was sweet and to the point! :-) Thanks for your input!
>
> Does this cause any issues interfacing with other systems?
>
> Hmmm... it appears not:
>
> https://dba.stackexchange.com/questions/105514/leap-second-in-database-system-postgresql-and-sql-server
>
> and
>
> https://stackoverflow.com/questions/31136211/how-to-handle-leap-seconds-in-oracle
>
> So, it would appear that neither Oracle nor Microsoft (RDBMS or OS/SQL
> Server) worry too much about this, so it would appear that I shouldn't
> either.
>
> However, I think this means that there's 27 seconds of my life that I
> never knew I had...
>
> Thanks again, saves me some work, and rgs,
>
>
> E...
>
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2025-01-27 21:54:41 | Re: Content of pg_publication using a local connection versus network connection? |
Previous Message | Shaheed Haque | 2025-01-27 21:34:57 | Re: Content of pg_publication using a local connection versus network connection? |