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 CAKU4AWoH2gLyK-ot7-YuXKbxmAWGoVsqGonH6e2noXM7Uib=6w@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)  (David Rowley <dgrowleyml@gmail.com>)
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

Looking forward to watching this change closely, thank you both David and Tom!
But I still don't understand what the faults my way have , do you mind telling the
details? 

--
Best Regards

pgsql-hackers by date:

Previous
From: Greg Nancarrow
Date:
Subject: Re: Re[3]: On login trigger: take three
Next
From: "tanghy.fnst@fujitsu.com"
Date:
Subject: RE: [HACKERS] logical decoding of two-phase transactions