The Hermit Hacker <scrappy@hub.org> writes:
> I have a database where, periodically, I get a query that is producing
> pg_noname files that are >1gig in size ... according to syslog, for that
> process:
> Sep 7 18:36:39 pgsql postgres[47078]: DEBUG: ExecRestrPos: node type 17 not supported
> Sep 7 18:36:39 pgsql postgres[47078]: DEBUG: ExecRestrPos: node type 17 not supported
> Sep 7 18:36:40 pgsql postgres[47078]: DEBUG: ExecRestrPos: node type 17 not supported
> Sep 7 18:36:56 pgsql postgres[47078]: DEBUG: ExecMarkPos: node type 17 not supported
> %
This is the planner bug that I was just alluding to in other email ---
the planner is trying to use a nestloop as the inner input to a
mergejoin, and that doesn't work :-(. But you only see the problem
if the outer side contains multiple matches to a single inside tuple.
I have a fix for current sources; let me see if I can retrofit it for
7.0.*.
regards, tom lane
