| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Richard Guo <guofenglinux(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Fix NULL pointer reference in _outPathTarget() |
| Date: | 2022-04-27 07:17:35 |
| Message-ID: | 28573897-7b7f-b559-923a-6125b107116e@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 22.04.22 16:18, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-04-27 08:13:12 | Re: BUG #17448: In Windows 10, version 1703 and later, huge_pages doesn't work. |
| Previous Message | Michael Paquier | 2022-04-27 07:09:20 | Re: avoid multiple hard links to same WAL file after a crash |