| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: session_replication_role origin vs local |
| Date: | 2015-05-31 11:55:12 |
| Message-ID: | CA+TgmoaYS_6PxU41vOp3bVtj3yDRnMPEocuL6NF0+5SniYTg_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, May 29, 2015 at 10:49 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> Does anyone know what the difference between the
> session_replication_role settings of 'origin' vs 'local' is supposed to
> be? AFAICT, the code treats them the same and has done since this
> feature was initially introduced.
I assume that 'local' is meant to be used on a replica node when
applying non-replicated changes that are only being done locally. But
that's just a guess.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-05-31 11:58:29 | Re: Join Filter vs. Index Cond (performance regression 9.1->9.2+/HEAD) |
| Previous Message | Robert Haas | 2015-05-31 11:51:59 | Re: Re: [GENERAL] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |