Warning When Creating FOR EACH STATEMENT Trigger On Logical Replication Subscriber Side

From: Avi Weinberg <AviW(at)gilat(dot)com>
To: "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Warning When Creating FOR EACH STATEMENT Trigger On Logical Replication Subscriber Side
Date: 2022-12-01 13:58:53
Message-ID: DB9PR07MB71804E876904F432ACCD253BCB149@DB9PR07MB7180.eurprd07.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Hackers,

There is no error or warning when creating FOR EACH STATEMENT trigger on Logical Replication subscriber side, but it is not doing anything. Shouldn't a warning be helpful?

CREATE TRIGGER set_updated_time_trig
AFTER INSERT OR UPDATE OR DELETE ON test
FOR EACH STATEMENT EXECUTE FUNCTION set_updated_time();

Thanks

IMPORTANT - This email and any attachments is intended for the above named addressee(s), and may contain information which is confidential or privileged. If you are not the intended recipient, please inform the sender immediately and delete this email: you should not copy or use this e-mail for any purpose nor disclose its contents to any person.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2022-12-01 14:24:43 Re: pgsql: Revoke PUBLIC CREATE from public schema, now owned by pg_databas
Previous Message Ronan Dunklau 2022-12-01 13:27:31 Re: Asynchronous execution support for Custom Scan