From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Uncle George <gatgul(at)voicenet(dot)com> |
Cc: | wieck(at)debis(dot)com (Jan Wieck), pgsql-hackers(at)postgreSQL(dot)org, pgsql-ports(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] RedHat6.0 & Alpha |
Date: | 1999-07-20 02:15:12 |
Message-ID: | 28663.932436912@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-ports |
Uncle George <gatgul(at)voicenet(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1999-07-20 02:46:51 | Re: [PORTS] RedHat6.0 & Alpha |
Previous Message | Uncle George | 1999-07-20 01:25:58 | Re: [PORTS] RedHat6.0 & Alpha |
From | Date | Subject | |
---|---|---|---|
Next Message | Unprivileged user | 1999-07-20 02:26:11 | Port Bug Report: INSERT INTO SELECT with join creates over 2000 temp files |
Previous Message | Bruce Momjian | 1999-07-20 02:07:35 | Re: [PORTS] Port to OS/2 completed ... |