| From: | Ashutosh Bapat <ashutosh(dot)bapat(at)enterprisedb(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | setting estate in ExecInitNode() itself |
| Date: | 2018-01-05 04:17:58 |
| Message-ID: | CAFjFpRccTimPYT7pdw4Naijd-hCVrb9gyBCdfiBDxr3yrtkPXA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Looking at ExecInitXYZ() functions, we can observe that every such
function has a statement like
XYZstate->ps.state = estate;
where it saves estate in the PlanState.
I am wondering why don't we instead save estate in ExecInitNode() itself like
result->estate = estate;
Are there any cases when a node wants to set a different estate there?
--
Best Wishes,
Ashutosh Bapat
EnterpriseDB Corporation
The Postgres Database Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2018-01-05 04:25:28 | Re: [HACKERS] VACUUM and ANALYZE disagreeing on what reltuples means |
| Previous Message | Stephen Frost | 2018-01-05 04:16:32 | Re: BUGFIX: standby disconnect can corrupt serialized reorder buffers |