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
On Tue, Jan 28, 2025 at 10:02 AM Nem Tudom wrote:
> Any help, advice, recommendations, URL-s, references &c. appreciated.
As others have said, we're using the POSIX AKA Unix time scale, as
almost all general purpose computer systems do. It's based on the UTC
time scale (the one that has SI secon
"Peter J. Holzer" writes:
> On 2025-01-27 21:01:59 +, Nem Tudom wrote:
>> I thought that the EPOCH was the number of seconds since 1970-01-01
>> 00:00:00? Is this incorrect?
> The POSIX standard mandates that leap seconds must be ignored. It's not
> really "number of seconds since 1970-01-01"
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/
On 2025-01-27 21:01:59 +, Nem Tudom wrote:
> I'm having trouble understanding matters related to TIMESTAMP(TZ)-s and leap
> seconds - my machine runs on UTC so as to remove any issues related to the
> zones.
>
> From here: https://en.wikipedia.org/wiki/Leap_second,
>
> There have been 27 leap
Hi all,
I'm having trouble understanding matters related to TIMESTAMP(TZ)-s and
leap seconds - my machine runs on UTC so as to remove any issues related
to the zones.
From here: https://en.wikipedia.org/wiki/Leap_second,
There have been 27 leap seconds added to UTC since 1972.
But, whe
On 1/27/25 13:01, Nem Tudom wrote:
Hi all,
I'm having trouble understanding matters related to TIMESTAMP(TZ)-s and
leap seconds - my machine runs on UTC so as to remove any issues related
to the zones.
From here: https://en.wikipedia.org/wiki/Leap_second,
There have been 27 leap seconds
