| From: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Assertion failure at standby promotion |
| Date: | 2013-05-06 10:10:31 |
| Message-ID: | 51878197.8000303@vmware.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 05.05.2013 12:13, Amit Langote wrote:
> Hello,
>
> I tried reproducing the scenario. Note that I did not archive xlogs
> (that is, archive_command = '/bin/true' and corresponding
> restore_command = '/bin/false'). I performed the steps you mentioned
> and could find following:
> [snip]
>>> [Standby-2]FATAL: could not receive data from WAL stream: ERROR: server switched off timeline 1 at 0/3510B14, but walsender already streamed up to 0/3512000
> Is this related to the assertion failure that you have reported?
Yep, same issue. If you compile with assertions disabled, you get that
error instead of the assertion. They both check for the same thing, it
was an oversight to have both.
- Heikki
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-05-06 10:54:06 | Re: 9.3 release notes suggestions |
| Previous Message | Heikki Linnakangas | 2013-05-06 10:08:45 | Re: Assertion failure at standby promotion |