Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series) - Mailing list pgsql-hackers

From Andy Fan
Subject Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series)
Date
Msg-id CAKU4AWp72VpFuo6e3GyGfTbGufvfLFmGtyzDGgZM5HF6mmZ3EA@mail.gmail.com
Whole thread Raw
In response to Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Keep notnullattrs in RelOptInfo (Was part of UniqueKey patch series)
List pgsql-hackers
On Tue, Jul 6, 2021 at 9:14 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> David Rowley <dgrowleyml@gmail.com> writes:
> > 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.
>
> As I said before, it hasn't progressed much past the handwaving stage,
> but it does seem like it's time to get it done.  I doubt I'll have any
> cycles for it during the commitfest, but maybe I can devote a block of
> time during August.
>
>                         regards, tom lane

Hi Tom:  do you get a chance to work on this? Looks like we have to fix
this one before we can move on to the uniquekey stuff.

-- 
Best Regards
Andy Fan



pgsql-hackers by date:

Previous
From: Greg Nancarrow
Date:
Subject: Re: Added schema level support for publication.
Next
From: Etsuro Fujita
Date:
Subject: Re: Defer selection of asynchronous subplans until the executor initialization stage