| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com>, Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it>, Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] session_replication_role = replica with TRUNCATE |
| Date: | 2018-01-18 16:30:24 |
| Message-ID: | c2fb1ed9-7e20-59a0-741c-36ea4eb46504@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/17/18 11:33, Petr Jelinek wrote:
>> P.S: I'm struggling to understand why we have two possible values of
>> session_replication_role settings that behave identically (origin and
>> local). I'm unable to see any difference according to the code or the
>> documentation, so I'm wondering if we should document that they are the
>> same.
>>
> It's for use by 3rd party tools (afaik both londiste and slony use it)
> to differentiate between replicated and not replicated changes.
I have committed some documentation updates and tests to cover this a
bit better.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vik Fearing | 2018-01-18 16:37:30 | Re: PATCH: psql tab completion for SELECT |
| Previous Message | Simon Riggs | 2018-01-18 16:07:20 | Re: Faster inserts with mostly-monotonically increasing values |