Re: [HACKERS] RedHat6.0 & Alpha
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] RedHat6.0 & Alpha |
Дата | |
Msg-id | 28663.932436912@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | RedHat6.0 & Alpha (Uncle George <gatgul@voicenet.com>) |
Ответы |
Re: [PORTS] Re: [HACKERS] RedHat6.0 & Alpha
Re: [PORTS] Re: [HACKERS] RedHat6.0 & Alpha |
Список | pgsql-ports |
Uncle George <gatgul@voicenet.com> writes: > In the regression test rules.sql there is this SQL command > update rtest_v1 set a = rtest_t3.a + 20 where b = rtest_t3.b; > Which causes my alpha port to go core. Yeah. This was reported by Pedro Lobo on 11 June, and we've been patiently waiting for Jan to decide what to do about it :-( You could stop the coredump by putting a test into ResolveNew: { *nodePtr = copyObject(n); + if (IsA(*nodePtr, Var)) ((Var *) *nodePtr)->varlevelsup = this_varlevelsup; } but what's not so clear is what's supposed to happen when the replacement item *isn't* a Var. I tried to convince myself that nothing needed to happen in that case, but wasn't successful. (Presumably the replacement expression contains no instances of the variable being replaced, so recursing into it with ResolveNew shouldn't be needed --- but maybe its varlevelsup values need adjusted?) regards, tom lane
В списке pgsql-ports по дате отправления: