Re: Trigger function on Warm Standby

From: Jerry Sievers <gsievers19(at)comcast(dot)net>
To: ning chan <ninchan8328(at)gmail(dot)com>
Cc: "pgsql-general\(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Trigger function on Warm Standby
Date: 2013-05-08 20:25:49
Message-ID: 87haid2p82.fsf@comcast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

ning chan <ninchan8328(at)gmail(dot)com> writes:

> Hi all,
>
> I have a Primary Standby setup with streaming replication.
> Trigger is created on a table, and all it does it to log a message.
>
> The trigger works as expected on Primary, however, I don't see the same on standby.
>
> I alter the table to have ENABLE ALWAYS TRIGGER, I verified the setting on both Primary and Standby which is set to A.
>
> Standby:
> -bash-4.1$ psql -c "select tgrelid, tgname, tgenabled from pg_trigger where tgname='processnodeafter'"
> ?tgrelid |????? tgname????? | tgenabled
> ---------+------------------+-----------
> ?? 19218 | processnodeafter | A
>
> Primary:
> postgres=# select tgrelid, tgname, tgenabled from pg_trigger where tgname='processnodeafter';
> ?tgrelid |????? tgname????? | tgenabled
> ---------+------------------+-----------
> ?? 19218 | processnodeafter | A
> (1 row)
>
> Can someone tell me if the trigger will never happen on the Standby server? Is it expected or am I missing some other
> settings?

It will not fire on a standby.

> Thanks~
> Ning
>

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2013-05-08 20:30:26 Re: pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4
Previous Message Evan D. Hoffman 2013-05-08 20:21:34 Re: pg_upgrade fails, "mismatch of relation OID" - 9.1.9 to 9.2.4