| From: | Dimitri Fontaine <dfontaine(at)hi-media(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Configuring synchronous replication |
| Date: | 2010-09-18 11:57:47 |
| Message-ID: | m239t7s1qc.fsf@hi-media.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> I've said COMMIT with no option because I believe that we have only two
> choices: commit or wait (perhaps forever), and IMHO waiting is not good.
>
> We can't ABORT, because we sent a commit to the standby.
Ah yes, I keep forgetting Sync Rep is not about 2PC. Sorry about that.
> Waiting might sound attractive. In practice, waiting will make all of
> your connections lock up and it will look to users as if their master
> has stopped working as well. (It has!). I can't imagine why anyone would
> ever want an option to select that; its the opposite of high
> availability. Just sounds like a serious footgun.
I guess that if there's a timeout GUC it can still be set to infinite
somehow. Unclear as the use case might be.
Regards,
--
dim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-09-18 18:37:01 | pgsql: Give a suitable HINT when an INSERT's data source is a RowExpr |
| Previous Message | Simon Riggs | 2010-09-18 08:50:41 | Re: Configuring synchronous replication |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2010-09-18 12:02:26 | Re: Progress indication prototype |
| Previous Message | Simon Riggs | 2010-09-18 08:50:41 | Re: Configuring synchronous replication |