Re: pgsql: instr_time: Represent time as an int64 on all platforms - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: instr_time: Represent time as an int64 on all platforms
Date
Msg-id 1543364.1674456919@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: instr_time: Represent time as an int64 on all platforms  (Andres Freund <andres@anarazel.de>)
Responses Re: pgsql: instr_time: Represent time as an int64 on all platforms  (Andres Freund <andres@anarazel.de>)
List pgsql-committers
Andres Freund <andres@anarazel.de> writes:
> On 2023-01-23 01:20:54 -0500, Tom Lane wrote:
>> Yeah, there was some discussion about that already:
>> https://www.postgresql.org/message-id/20230121190303.7xjiwdg3gvb62lu3@awork3.anarazel.de

> I was thinking of starting a starting a separate thread about it - it's
> mostly a plpython issue, the fact that my commit caused the compilation
> failure is somewhat random.

True.  It also seems odd to me that per your analysis, we fixed
the _POSIX_C_SOURCE conflict on 4 Aug 2011 and then broke it again
on 18 Dec 2011, yet nobody has noticed for nigh a dozen years ---
there has to be some other element in there.

            regards, tom lane



pgsql-committers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pgsql: instr_time: Represent time as an int64 on all platforms
Next
From: David Rowley
Date:
Subject: pgsql: Harden new parallel string_agg/array_agg regression test