| From: | Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: NoMovementScanDirection in heapgettup() and heapgettup_pagemode() |
| Date: | 2017-08-29 03:14:28 |
| Message-ID: | CAD__OugcMktg-ePOpNnnSB3pqk3UAJoJHTANjt=5HpVyHmXOYQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Aug 28, 2017 at 5:50 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I think that's probably dead code given that ExecutorRun short-circuits
> everything for NoMovementScanDirection. There is some use of
> NoMovementScanDirection for indexscans, to denote an unordered index,
> but likely that could be got rid of too. That would leave us with
> NoMovementScanDirection having no other use except as a do-nothing
> flag for ExecutorRun.
>
> regards, tom lane
Thanks, Tom, yes it seems to be a dead code.
--
Thanks and Regards
Mithun C Y
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-08-29 04:26:03 | Re: [Proposal] Allow users to specify multiple tables in VACUUM commands |
| Previous Message | David G. Johnston | 2017-08-29 03:07:32 | Re: show "aggressive" or not in autovacuum logs |