Re: [PATCHES] Small fix for _equalValue() - Mailing list pgsql-hackers

From Thomas Lockhart
Subject Re: [PATCHES] Small fix for _equalValue()
Date
Msg-id 3C8A9E14.D6A7E5EC@fourpalms.org
Whole thread Raw
In response to Re: [PATCHES] Small fix for _equalValue()  (Thomas Lockhart <thomas@fourpalms.org>)
Responses Re: [PATCHES] Small fix for _equalValue()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
...
> That's because I already committed the other changes he pointed out ;-).
> But yeah, we seem to be copy-clean again.

I had thought that you objected to the guard code in the copy functions
since nodes should not have had the content they did. And afaik I have
now fixed the upstream problems with the content.

Had you changed you mind about the necessity for the guard code? Why did
those patches get applied if the only feedback in the thread was that
the problem did not lie there?

Or are we talking about two different parts of the patch submission? I'm
a bit confused as to the current state of the code tree...
                    - Thomas


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Adding qualification conditions to EXPLAIN output
Next
From: Bruce Momjian
Date:
Subject: Re: Adding qualification conditions to EXPLAIN output