Re: pg_ctl/miscinit: print "MyStartTime" as a long long instead of long to avoid 2038 problem.

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Max Johnson <max(dot)johnson(at)novatechautomation(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_ctl/miscinit: print "MyStartTime" as a long long instead of long to avoid 2038 problem.
Date: 2024-10-07 19:17:06
Message-ID: ZwQzsqbm2fBsZ8xS@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Oct 07, 2024 at 02:00:05PM -0500, Nathan Bossart wrote:
> I refrained from introducing INT64_HEX_FORMAT/UINT64_HEX_FORMAT in c.h
> because I felt there was a nonzero chance of that causing problems with
> third-party code on the back-branches. We could probably add them for v18,
> though.

Like so...

--
nathan

Attachment Content-Type Size
0001-add-INT64_HEX_FORMAT-and-UINT64_HEX_FORMAT.patch text/plain 3.8 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2024-10-07 19:37:35 Re: pg_upgrade check for invalid databases
Previous Message Nathan Bossart 2024-10-07 19:00:05 Re: pg_ctl/miscinit: print "MyStartTime" as a long long instead of long to avoid 2038 problem.