Re: pgsql: instr_time: Represent time as an int64 on all platforms

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: instr_time: Represent time as an int64 on all platforms
Date: 2023-01-23 06:55:19
Message-ID: 1543364.1674456919@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Andres Freund <andres(at)anarazel(dot)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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2023-01-23 08:32:11 pgsql: Harden new parallel string_agg/array_agg regression test
Previous Message Andres Freund 2023-01-23 06:46:47 Re: pgsql: instr_time: Represent time as an int64 on all platforms