| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
| 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-22 14:18:00 |
| Message-ID: | 3688649.1650637080@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2022-04-22 14:23:44 | Re: How to simulate sync/async standbys being closer/farther (network distance) to primary in core postgres? |
| Previous Message | Peter Eisentraut | 2022-04-22 14:16:02 | Re: Fix NULL pointer reference in _outPathTarget() |