| From: | Steven Parkes <smparkes(at)smparkes(dot)net> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: replay doesn't catch up with receive on standby |
| Date: | 2011-04-19 01:28:40 |
| Message-ID: | 8CC276E6-801B-4CCA-9F2E-836177F1C15D@smparkes.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Did you run query on the standby?
Yup. Both standbys. They both responded the same way.
> If yes, I guess that query conflict prevented
> the reply location from advancing.
> http://www.postgresql.org/docs/9.0/static/hot-standby.html#HOT-STANDBY-CONFLICT
The standbys were idle and this was a persistent state. I restarted the standbys and they stayed in this state. Am I missing something? I thought these conflicts were related to queries against the standbys but there shouldn't have been any that I'm aware. Certainly none should survive a restart ...
Am I missing something about the conflict?
It also seems notable that a new commit on the master cleared the issue ... Does that seem like the hot standby conflict case?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2011-04-19 01:59:23 | Re: replay doesn't catch up with receive on standby |
| Previous Message | Fujii Masao | 2011-04-19 01:18:04 | Re: replay doesn't catch up with receive on standby |