Re: Fix NULL pointer reference in _outPathTarget() - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Fix NULL pointer reference in _outPathTarget()
Date
Msg-id 28573897-7b7f-b559-923a-6125b107116e@enterprisedb.com
Whole thread Raw
In response to Re: Fix NULL pointer reference in _outPathTarget()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 22.04.22 16:18, Tom Lane wrote:
> Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes:
>> On 20.04.22 18:53, Tom Lane wrote:
>>> Yeah, that's another way to do it.  I think though that the unresolved
>>> question is whether or not we want the field name to appear in the output
>>> when the field is null.  I believe that I intentionally made it not appear
>>> originally, so that that case could readily be distinguished.  You could
>>> argue that that would complicate life greatly for a _readPathTarget()
>>> function, which is true, but I don't foresee that we'll need one.
> 
>> We could adapt the convention to print NULL values as "<>", like
> 
> Works for me.

done



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: avoid multiple hard links to same WAL file after a crash
Next
From: Michael Paquier
Date:
Subject: Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work.