From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Ramanujam H S Iyengar" <hals_ramu(at)hotmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: What will (Plan*) ()->chgParam contain ??? |
Date: | 2004-02-23 15:09:52 |
Message-ID: | 27972.1077548992@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Ramanujam H S Iyengar" <hals_ramu(at)hotmail(dot)com> writes:
> Can some one tell me what and when (Plan*)()->chgParam will contain ?
It's either an integer List or a Bitmapset, depending on what version
you are looking at, but in either case it contains the integer IDs of
PARAM_EXEC Param slots that have changed recently. This is used to
force recalculation of those plan nodes (and only those plan nodes)
that depend on the parameter(s) that have changed. AFAIR the PARAM_EXEC
mechanism is only used for passing values into and out of sub-selects,
but someday it might have more general use.
See the related plan fields extParam, allParam, setParam, parParam.
These are documented reasonably well (at least in current sources)
in plannodes.h and primnodes.h.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Lamar Owen | 2004-02-23 15:38:26 | Re: Heads up: 7.3.6 and 7.4.2 coming soon |
Previous Message | Kenneth Marshall | 2004-02-23 14:32:55 | Re: [PATCHES] update i386 spinlock for hyperthreading |