| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | peter(dot)trautmeier(at)gmx(dot)de |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: ecxt_scantuple has wrong TupleDesc |
| Date: | 2007-12-17 16:27:09 |
| Message-ID: | 21394.1197908829@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
peter(dot)trautmeier(at)gmx(dot)de writes:
> I wonder why my ecxt_scantuple has a TupleDesc matching the subplan's
> tlist, not my plan's tlist.
That's the way it's supposed to be --- the scantuple slot is for
scanning your subplan's output.
> I have written a new executor node Foo, with corresponding ExecFoo and make_foo functions. I have also written a new Expr type called Bar, along with a ExecEvalBar.
> In make_foo I append some Bar columns. When I try to evaluate the Bar columns in ExecFoo via ExecProject, I need the Bar columns to access each other.
That makes no sense at all. ExecProject can't be expected to access
output columns of the current node --- they haven't been computed yet.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oleg Bartunov | 2007-12-17 16:28:19 | Board for developers |
| Previous Message | Tom Lane | 2007-12-17 16:06:14 | Re: pgindent issue with EXEC_BACKEND-only typedefs |