| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: parallelize queries containing initplans |
| Date: | 2017-11-10 20:03:32 |
| Message-ID: | 5073.1510344212@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Nov 10, 2017 at 2:24 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Also, I wonder whether the InvalidOid hack in SS_assign_special_param
>> requires commentary. It might be safer to use a valid type OID there,
>> perhaps VOIDOID or INTERNALOID.
> There is existing precedent for using InvalidOid to denote the absence
> of a parameter -- cf. copyParamList, SerializeParamList.
OK, fair enough. I was concerned that this was adding a corner case
not otherwise seen with Params, but evidently not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-11-10 20:10:36 | Re: LDAP URI decoding bugs |
| Previous Message | Thomas Munro | 2017-11-10 19:42:55 | Re: Planning counters in pg_stat_statements |