| From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Updated version of pg_receivexlog |
| Date: | 2011-10-24 14:12:34 |
| Message-ID: | CAJKUy5ghp-T04Y5jVchBiSTgRJENZ=8JNrYbTMPf=_Qi6BivCw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Oct 24, 2011 at 7:40 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>
>> synchronous_standby_names='*' is prone to such confusion in general, but it
>> seems that it's particularly surprising if a running pg_basebackup lets a
>> commit in synchronous replication to proceed. Maybe we just need a warning
>> in the docs. I think we should advise that synchronous_standby_names='*' is
>> dangerous in general, and cite this as one reason for that.
>
> Hmm. i think this is common enough that we want to make sure we avoid
> it in code.
>
> Could we pass a parameter from the client indicating to the master
> that it refuses to be a sync slave? An optional keyword to the
> START_REPLICATION command, perhaps?
>
can't you execute "set synchronous_commit to off/local" for this connection?
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-10-24 14:16:49 | Re: Updated version of pg_receivexlog |
| Previous Message | Tom Lane | 2011-10-24 14:05:15 | Re: termination of backend waiting for sync rep generates a junk log message |