From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: TRAP: FailedAssertion("!(hassrf)", File: "nodeProjectSet.c", Line: 180) |
Date: | 2017-02-02 03:32:52 |
Message-ID: | 30214.1486006372@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2017-02-02 00:09:03 +0100, Erik Rijkers wrote:
>> Something is broken in HEAD:
> Hm. Indeed.
> The issue is that we're generating ProjectSet nodes instead of Result
> for the top-level nodes - but we currently assume that ProjectSet nodes
> actually contain sets. I'm tentatively in favor of generating proper
> Result nodes in this case, rather than allowing this in ProjectSet - on
> the other hand, it works after removing that Assert().
> Tom, do you have an opinion?
Yes, it's broken. split_pathtarget_at_srfs seems to be doing the right
thing, but then something later is recombining the last two steps.
I should be able to find it soon.
Does it really work without the Assert? I'd think you'd get srf-
where-not-supported errors if the SRF isn't at top level.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Euler Taveira | 2017-02-02 03:45:46 | Re: Logical Replication and Character encoding |
Previous Message | Michael Paquier | 2017-02-02 03:20:13 | Re: Commit fest 2017-01 will begin soon! |