From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Generate index-only scan tuple descriptor from the plan node's i |
Date: | 2011-10-11 22:13:15 |
Message-ID: | E1RDkZX-0001sv-Gp@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Generate index-only scan tuple descriptor from the plan node's indextlist.
Dept. of second thoughts: as long as we've got that tlist hanging around
anyway, we can apply ExecTypeFromTL to it to get a suitable descriptor for
the ScanTupleSlot. This is a nicer solution than the previous one because
it eliminates some hard-wired knowledge about btree name_ops, and because
it avoids the somewhat shaky assumption that we needn't set up the scan
tuple descriptor in EXPLAIN_ONLY mode. It doesn't change what actually
happens at run-time though, and I'm still a bit nervous about that.
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/cb6771fb32cbdb11c8d84b7d62ee940bdba38d52
Modified Files
--------------
src/backend/executor/nodeIndexonlyscan.c | 68 +++++++-----------------------
1 files changed, 16 insertions(+), 52 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-10-11 22:41:50 | pgsql: Add comment on why pulling data from a "name" index column can't |
Previous Message | Bruce Momjian | 2011-10-11 22:04:34 | pgsql: Improve entab's Makefile install entry. |