Re: [PATCH] session_replication_role = replica with TRUNCATE - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: [PATCH] session_replication_role = replica with TRUNCATE
Date
Msg-id 4fafb6b6-f79d-5563-df19-837b2c14e9be@2ndquadrant.com
Whole thread Raw
In response to Re: [PATCH] session_replication_role = replica with TRUNCATE  (Marco Nenciarini <marco.nenciarini@2ndquadrant.it>)
Responses Re: [PATCH] session_replication_role = replica with TRUNCATE  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On 29/12/17 16:53, Marco Nenciarini wrote:
> Il 29/12/17 15:14, Petr Jelinek ha scritto:
>>
>> May be worth documenting that the session_replication_role also affects
>> TRUNCATE's interaction with FKs in config.sgml.
>>
> 
> The current documentation of session_replication_role GUC is:
> 
>     Controls firing of replication-related triggers and rules for the
>     current session. Setting this variable requires superuser privilege
>     and results in discarding any previously cached query plans.
>     Possible values are origin (the default), replica and local.
>     See ALTER TABLE for more information.
> 
> It doesn't speak about foreign keys or referential integrity, but only
> about triggers and rules. I don't think that it's worth to add a special
> case for truncate, unless we want to expand/rewrite the documentation to
> specify all the effects in the details.
> 

The effects on foreign keys is implied by the fact that for DML it's
implemented using triggers, but that's not true for TRUNCATE. In any
case it does not hurt to mention the FKs explicitly rather than
implicitly here.

-- 
  Petr Jelinek                  http://www.2ndQuadrant.com/
  PostgreSQL Development, 24x7 Support, Training & Services


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Deadlock in multiple CIC.
Next
From: Andres Freund
Date:
Subject: Re: Condition variable live lock