Re: [PATCH] session_replication_role = replica with TRUNCATE

Поиск
Список
Период
Сортировка
От Marco Nenciarini
Тема Re: [PATCH] session_replication_role = replica with TRUNCATE
Дата
Msg-id 93d19a52-4390-4f42-46e2-413b13542927@2ndquadrant.it
обсуждение исходный текст
Ответ на Re: [PATCH] session_replication_role = replica with TRUNCATE  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
Ответы Re: [PATCH] session_replication_role = replica with TRUNCATE  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
Список pgsql-hackers
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.

Regards,
Marco

--
Marco Nenciarini - 2ndQuadrant Italy
PostgreSQL Training, Services and Support
marco.nenciarini@2ndQuadrant.it | www.2ndQuadrant.it


Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: Basebackups reported as idle
Следующее
От: Tom Lane
Дата:
Сообщение: Possible hole in Windows directory restrictions?