From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: NoMovementScanDirection in heapgettup() and heapgettup_pagemode() |
Date: | 2017-08-28 12:20:59 |
Message-ID: | 3396.1503922859@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com> writes:
> I was trying to study NoMovementScanDirection part of heapgettup() and
> heapgettup_pagemode(). If I am right there is no test in test suit to
> hit this code. I did run make check-world could not hit it. Also,
> coverage report in
> https://coverage.postgresql.org/src/backend/access/heap/heapam.c.gcov.html
> shows this part of the code is not hit. Can somebody please help me to
> understand this part of the code and how to test same?
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
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2017-08-28 12:26:38 | Re: [HACKERS] [postgresql 10 beta3] unrecognized node type: 90 |
Previous Message | Michael Paquier | 2017-08-28 12:06:09 | Re: standby server crashes hard on out-of-disk-space in HEAD |