Re: [7.0.2] node type 17 not supported ...
От | The Hermit Hacker |
---|---|
Тема | Re: [7.0.2] node type 17 not supported ... |
Дата | |
Msg-id | Pine.BSF.4.21.0009072116070.527-100000@thelab.hub.org обсуждение исходный текст |
Ответ на | Re: [7.0.2] node type 17 not supported ... (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [7.0.2] node type 17 not supported ...
|
Список | pgsql-hackers |
On Thu, 7 Sep 2000, Tom Lane wrote: > 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.*. that would be perfect ... if we can get that retrofit'd, I'd be quite tempted to put out a 7.0.3 for this, considering that its obviously not an isolated incident ;( Thanks ...
В списке pgsql-hackers по дате отправления: