Re: LLVM jit and matview

From: Andres Freund <andres(at)anarazel(dot)de>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Dmitry Dolgov <9erthalion6(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, PostgreSQL mailing lists <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: LLVM jit and matview
Date: 2018-07-25 02:49:56
Message-ID: 20180725024956.6gxqscgk5fmuqbb7@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

On 2018-07-10 09:19:58 +0900, Michael Paquier wrote:
> On Mon, Jul 09, 2018 at 04:04:11PM +0200, Dmitry Dolgov wrote:
> > # matview.sql
> > ...
> > =# REFRESH MATERIALIZED VIEW CONCURRENTLY mvtest_tm;
> > server closed the connection unexpectedly
> > This probably means the server terminated abnormally
> > before or while processing the request.
> > The connection to the server was lost. Attempting reset: Failed.
>
> Problem reproduced here with exactly the same stack. Here is a simple
> SQL sequence:
> create table aa (a int);
> create materialized view aam as select * from aa;
> create unique index aami on aam(a);
> insert into aa values (generate_series(1,100000));
> refresh materialized view CONCURRENTLY aam;

FWIW, this doesn't crash for me, using a trunk checkout for LLVM. I'll
try older ones, as soon as they finish rebuilding. But perhaps you could
re-verify that this still is an issue on recent PG checkouts? And which
version of LLVM are you guys using?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2018-07-25 02:59:07 Re: BUG #15290: Stuck Parallel Index Scan query
Previous Message Andres Freund 2018-07-25 02:08:05 Re: BUG #15290: Stuck Parallel Index Scan query

Browse pgsql-hackers by date

  From Date Subject
Next Message Imai, Yoshikazu 2018-07-25 02:53:57 RE: Locking B-tree leafs immediately in exclusive mode
Previous Message Michael Paquier 2018-07-25 01:06:32 Re: Add SKIP LOCKED to VACUUM and ANALYZE