Postgres Pro
Downloads
Home   >   mailing lists

Re: pgsql: Fix calculation of plan node extParams to account for the - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Fix calculation of plan node extParams to account for the
Date
Msg-id 21744.1149198794@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Fix calculation of plan node extParams to account for the  ("Jackie Leng" <lengjianquan@163.com>)
List pgsql-committers
Tree view 
"Jackie Leng" <lengjianquan@163.com> writes:
> So, my question is why not just add a bms_intersect in the second occasion
> just like the first one? Do we need to change so much?

finalize_plan already has a bms_intersect, but it's further down in the
routine (to share code instead of duplicating it in each of the switch
cases) --- in CVS HEAD, line 1199.  This is not relevant to the patch
AFAICS.

            regards, tom lane

pgsql-committers by date:

Previous
From: fxjr@pgfoundry.org (User Fxjr)
Date:
Subject: npgsql - Npgsql: 2006-06-01 Francisco Figueiredo Jr.
Next
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Back-port Postgres 7.4 spinlock code into 7.3 branch.