Horton

Re: plpython vs _POSIX_C_SOURCE

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: Andres Freund <andres@anarazel.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Noah Misch <noah@leadboat.com>, pgsql-hackers@postgresql.org, Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Andrew Dunstan <andrew@dunslane.net>
Date: 2023-01-25T08:52:23Z
Lists: pgsql-hackers 
Hi,

On 2023-01-24 23:37:44 -0500, Tom Lane wrote:
> Andres Freund <andres@anarazel.de> writes:
> > Patches attached.
> 
> +1 for 0001.

Cool, will push tomorrow.


> I'm still nervous about 0002.  However, maybe the cases that we had trouble
> with are legacy issues that nobody cares about anymore in 2023.  We can
> always look for another answer if we get complaints, I guess.

Yea, it's a patch that should be easily revertable, if it comes to that. I'll
add a note to the commit message about potentially needing to do that if
there's not easily addressed fallout.

Greetings,

Andres Freund

Commits

  1. plpython: Avoid the need to redefine *printf macros

  2. plpython: Stop undefining _POSIX_C_SOURCE, _XOPEN_SOURCE