Re: BUG #15114: logical decoding Segmentation fault

From: Andres Freund <andres(at)anarazel(dot)de>
To: Петър Славов <pet(dot)slavov(at)gmail(dot)com>
Cc: Petr Jelinek <petr(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15114: logical decoding Segmentation fault
Date: 2018-03-26 21:06:43
Message-ID: 20180326210643.xzoatxsyq2rptoc5@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2018-03-26 22:59:12 +0200, Петър Славов wrote:
> Hi Andres,
>
> Alvaro, Petr: If I understand correctly what happens here is that some
> > *other* column than the replica identity has a predicate with a full
> > blown SQL function. We shouldn't evaluate arbitrary code like that
> > inside the otuput plugin!
> >
>
> Not sure what you mean here, but in my case the replica identity is a
> regular integer primary key, without any functions as predicates in the
> index or anything else.

Turns out it it's not the replica identity index that's the problem,
it's *another* index with a WHERE clause that evaluates an SQL
function. That's a bug that needs to be fixed. But you might be able to
work around it for now by simplifying your WHERE clauses for the indexes
to not use SQL functions.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Петър Славов 2018-03-26 21:19:02 Re: BUG #15114: logical decoding Segmentation fault
Previous Message Alvaro Herrera 2018-03-26 21:04:17 Re: BUG #15114: logical decoding Segmentation fault