pgsql: Doc: add some commentary about ExecutorRun's NoMovement special

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Doc: add some commentary about ExecutorRun's NoMovement special
Date: 2024-12-10 22:17:59
Message-ID: E1tL8YI-0026Ed-Qy@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Doc: add some commentary about ExecutorRun's NoMovement special case.

Robert Haas expressed concern about whether commit 3eea7a0c9 exposed
the parallel-execution machinery to a case it isn't tested for, namely
a second non-parallel execution of a plan after a parallel execution.
Investigation shows that that can't happen because of pquery.c's
manipulation of the scan direction, but it sure wasn't obvious to
start with. Add some commentary about that.

Discussion: https://postgr.es/m/CA+TgmoagyKQy=HFw+wLo0AKTYWHui+iKswZ8Jnqqd-cFby-WVg@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/982890530379235974a7e99fd72e862ae40f1400

Modified Files
--------------
src/backend/executor/execMain.c | 11 ++++++++++-
1 file changed, 10 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message David Rowley 2024-12-10 22:32:37 pgsql: Speedup Hash Joins with dedicated functions for ExprState hashin
Previous Message Noah Misch 2024-12-10 21:54:43 pgsql: Fix elog(FATAL) before PostmasterMain() or just after fork().