| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add pg_walinspect function with block info columns |
| Date: | 2023-03-18 01:18:59 |
| Message-ID: | ZBURg3HSuMY7PKgj@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Mar 17, 2023 at 06:09:05PM -0700, Peter Geoghegan wrote:
>> This said, your point about having rec_blk_ref reported as an empty
>> string rather than NULL if there are no block references does not feel
>> natural to me, either.. Reporting NULL would be better.
>
> You have it backwards. It outputs an empty string right now. I want to
> change that, so that it outputs NULLs instead.
My previous paragraph means exactly the same? I have just read what I
wrote again. Twice. So, yes, I agree with this point. Sorry if my
words meant the contrary to you. :)
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2023-03-18 03:40:05 | Re: Amcheck verification of GiST and GIN |
| Previous Message | Peter Geoghegan | 2023-03-18 01:09:05 | Re: Add pg_walinspect function with block info columns |