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

On Wed, Nov 27, 2019 at 5:20 PM Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com> wrote:
> 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.

A bit of investigation showed that this is caused by commit
ff11e7f4b9ae017585c3ba146db7ba39c31f209a. I haven't yet looked at the
commit in any detail, though.

Best regards,
Etsuro Fujita