On Tue, Apr 10, 2018 at 03:15:47PM +0900, Amit Langote wrote:
> I too thought the same yesterday, as I couldn't see the commit even after
> about 35 minutes Alvaro actually had sent the email to -hackers (quoted
> above).
Bah, of course. Sorry for the noise.
--
Michael
signature.asc
Description:
On 2018/04/10 13:55, Michael Paquier wrote:
> On Mon, Apr 09, 2018 at 10:59:48AM -0300, Alvaro Herrera wrote:
>> Amit Langote wrote:
>>> I have reproduced this and found that the problem is that
>>> perform_pruning_combine_step forgets to *copy* the bitmapset of the first
>>> step in the handling o
On Mon, Apr 09, 2018 at 10:59:48AM -0300, Alvaro Herrera wrote:
> Amit Langote wrote:
>> I have reproduced this and found that the problem is that
>> perform_pruning_combine_step forgets to *copy* the bitmapset of the first
>> step in the handling of an COMBINE_INTERSECT step.
>
> Pushed, thanks A
On 2018/04/09 22:59, Alvaro Herrera wrote:
> Hello,
>
> Amit Langote wrote:
>
>> I have reproduced this and found that the problem is that
>> perform_pruning_combine_step forgets to *copy* the bitmapset of the first
>> step in the handling of an COMBINE_INTERSECT step.
>
> Pushed, thanks Amit an
Hello,
Amit Langote wrote:
> I have reproduced this and found that the problem is that
> perform_pruning_combine_step forgets to *copy* the bitmapset of the first
> step in the handling of an COMBINE_INTERSECT step.
Pushed, thanks Amit and Andreas!
--
Álvaro Herrerahttps://www.
On 2018/04/09 17:50, Amit Langote wrote:
> Attached fixes that. I see that Michael Paquier has added this to the
> open items list. Thanks, Michael.
>
> https://wiki.postgresql.org/wiki/PostgreSQL_11_Open_Items#Open_Issues
Oops, it was Tom who added that. Thank you!
Regards,
Amit
Hi Andreas.
On 2018/04/08 3:33, Andreas Seltenreich wrote:
> Hi,
>
> testing with master at 039eb6e92f yielded another query triggering an
> assertion.
Thanks for the report.
> Backtrace and query against the regression database below.
> #0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/
Hi,
testing with master at 039eb6e92f yielded another query triggering an
assertion. Backtrace and query against the regression database below.
regards,
Andreas
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
#1 0x7f25474cf42a in __GI_abort () at abort.c:89
#2 0x
