| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: is sync rep stalled? |
| Date: | 2010-10-05 09:49:50 |
| Message-ID: | 4CAAF4BE.1080105@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05.10.2010 12:47, Fujii Masao wrote:
> I have another question: when should the waiting transactions resume?
> It's a moment the standby has connected to the master? It's a moment
> the standby has caught up with the master? For no data loss, the
> latter seems to be required. Right?
Yep.
> The third question: if the WAL file is unfortunately recycled when a
> transaction waits for that WAL file to be shipped forever, how should
> that transaction behave? Still waiting? Cause PANIC? Give up waiting?
> For no data loss, ISTM that the second should be chosen. Right?
Right, it should keep waiting.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rajesh Kumar Mallah | 2010-10-05 10:16:09 | Re: streaming replication question |
| Previous Message | Fujii Masao | 2010-10-05 09:47:17 | Re: is sync rep stalled? |