As proposed the complete changes to pg_trigger and pg_rewrite

From: Jan Wieck <JanWieck(at)Yahoo(dot)com>
To: PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org>
Subject: As proposed the complete changes to pg_trigger and pg_rewrite
Date: 2007-03-16 02:14:53
Message-ID: 45F9FD9D.8040505@Yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

For discussion:

Attached is the completed patch that changes pg_trigger and extends
pg_rewrite in order to allow triggers and rules to be defined with
different, per session controllable, behaviors for replication purposes.

This will allow replication systems like Slony-I and, as has been stated
on pgsql-hackers, other products to control the firing mechanism of
triggers and rewrite rules without modifying the system catalog directly.

The firing mechanisms are controlled by a new superuser-only GUC
variable, session_replication_role, together with a change to
pg_trigger.tgenabled and a new column pg_rewrite.ev_enabled. Both
columns are a single char data type now (tgenabled was a bool before).
The possible values in these attributes are:

'O' - Trigger/Rule fires when session_replication_role is "origin"
(default) or "local". This is the default behavior.

'D' - Trigger/Rule is disabled and fires never

'A' - Trigger/Rule fires always regardless of the setting of
session_replication_role

'R' - Trigger/Rule fires when session_replication_role is "replica"

The GUC variable can only be changed as long as the system does not have
any saved SPI plans. This will prevent changing the session role and
accidentally executing stored procedures or functions that have plans
cached that expand to the wrong query set due to differences in the rule
firing semantics.

The SQL syntax for changing a triggers/rules firing semantics is

ALTER TABLE <tabname> <when> TRIGGER|RULE <name>;

<when> ::= ENABLE | ENABLE ALWAYS | ENABLE REPLICA | DISABLE

psql's \d command as well as pg_dump are extended in a backward
compatible fashion.

Any volunteers to do the corresponding documentation changes should this
patch be accepted?

Jan

--
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#================================================== JanWieck(at)Yahoo(dot)com #

Attachment Content-Type Size
enable_replica_trigger_and_rule.diff text/plain 54.2 KB

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-03-16 02:36:38 Re: UPDATE using sub selects
Previous Message Tom Lane 2007-03-16 01:08:11 pltcl vs. multilib machines

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2007-03-16 03:16:10 Re: As proposed the complete changes to pg_trigger and pg_rewrite
Previous Message Tom Lane 2007-03-15 23:53:17 Re: remove psql support for ancient copy syntax