| From: | Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> |
|---|---|
| To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, "Hou, Zhijie" <houzj(dot)fnst(at)cn(dot)fujitsu(dot)com>, Floris Van Nee <florisvannee(at)optiver(dot)com> |
| Subject: | Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series) |
| Date: | 2021-07-07 05:08:34 |
| Message-ID: | CAKU4AWqz75w-M=Er=_cSou519YvCMDv=GyuKmczYgd7GVwDNxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
>
>
> For example: SELECT nullablecol FROM tab WHERE nullablecol = <value>;
>
> If the equality operator is strict then the nullablecol can be NULL in
> the WHERE clause but not in the SELECT list. Tom's idea should allow
> us to determine both of those things but your idea cannot tell them
> apart, so, in theory at least, Tom's idea seems better to me.
>
> David
>
That's really something I can't do, thanks for the explanation.
--
Best Regards
Andy Fan (https://www.aliyun.com/)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Nancarrow | 2021-07-07 05:24:24 | Re: row filtering for logical replication |
| Previous Message | Michael Paquier | 2021-07-07 05:08:20 | Re: [PATCH] Pull general SASL framework out of SCRAM |