| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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-06 09:34:26 |
| Message-ID: | CAApHDvrRwhWCPKUD5H-EQoezHf=fnUUsPgTAnXsEOV8f8SF7XQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, 4 Jul 2021 at 02:08, Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com> wrote:
> I'd start to work on UniqueKey again, it would be great that we can target it
> to PG 15. The attached patch is just for the notnull_attrs. Since we can't say
> a column is nullable or not without saying in which resultset, so I think attaching
> it to RelOptInfo is unavoidable. Here is how my patch works.
I'd also like to see this work progress for PG15. My current thoughts
are that Tom as mentioned another way to track nullability inside Var.
It would be a fairly big task to do that.
Tom, I'm wondering if you might get a chance to draw up a design for
what you've got in mind with this? I assume adding a new field in
Var, but I'm drawing a few blanks on how things might work for equal()
when one Var has the field set and another does not.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-07-06 09:50:14 | Re: "debug_invalidate_system_caches_always" is too long |
| Previous Message | Amit Kapila | 2021-07-06 09:33:32 | Re: Skipping logical replication transactions on subscriber side |