| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | 9erthalion6(at)gmail(dot)com, alvherre(at)2ndquadrant(dot)com, andrew(dot)dunstan(at)2ndquadrant(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Cache lookup errors with functions manipulation object addresses |
| Date: | 2019-09-25 05:02:03 |
| Message-ID: | 20190925050203.GH1815@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 24, 2019 at 03:25:08PM +0900, Kyotaro Horiguchi wrote:
> In 0003, empty string and NULL are not digtinguishable in psql
> text output. It'd be better that the regression test checks that
> the return is actually NULL using "is NULL" or "\pset null
> '<null>'" or something like.
For a patch whose purpose is to check after NULL, I missed to consider
that... Thanks! I have just added a "\pset null NULL" because that's
less bulky than the other option, and all the results properly show
NULL, without any empty strings around. I am not sending a new patch
set just for that change though, and the most recent version is here:
https://github.com/michaelpq/postgres/tree/objaddr_nulls
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2019-09-25 05:03:52 | Re: Hypothetical indexes using BRIN broken since pg10 |
| Previous Message | Michael Paquier | 2019-09-25 04:47:27 | Re: Fix example in partitioning documentation |