Re: BUG #16139: Assertion fails on INSERT into a postgres_fdw' table with two AFTER INSERT triggers

From: Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>
To: exclusion(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16139: Assertion fails on INSERT into a postgres_fdw' table with two AFTER INSERT triggers
Date: 2019-11-27 08:20:19
Message-ID: CAPmGK15ceMM69qh3==qh6-sZzwxPnBsJdNUqUR82PGbUUEjctg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Nov 27, 2019 at 4:21 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> The following script:
> CREATE EXTENSION postgres_fdw;
> CREATE SERVER loopback FOREIGN DATA WRAPPER postgres_fdw OPTIONS (dbname
> 'postgres');
> CREATE USER MAPPING FOR CURRENT_USER SERVER loopback;
> CREATE TABLE loc2 (f1 int);
> CREATE FOREIGN TABLE rem2 (f1 int) SERVER loopback OPTIONS(table_name
> 'loc2');
> CREATE OR REPLACE FUNCTION trigger_data() RETURNS trigger
> LANGUAGE plpgsql AS 'begin return NEW; end;';
>
> CREATE TRIGGER trigger1 AFTER INSERT ON rem2 FOR EACH ROW EXECUTE PROCEDURE
> trigger_data();
> CREATE TRIGGER trigger2 AFTER INSERT ON rem2 FOR EACH ROW EXECUTE PROCEDURE
> trigger_data();
> INSERT INTO rem2 VALUES(1);
>
> raises the assertion:

Reproduced. Will look into this.

Best regards,
Etsuro Fujita

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Dean Rasheed 2019-11-27 09:26:11 Re: Failed assertion clauses != NIL
Previous Message PG Bug reporting form 2019-11-27 07:20:45 BUG #16139: Assertion fails on INSERT into a postgres_fdw' table with two AFTER INSERT triggers