| From: | Greg Stark <gsstark(at)mit(dot)edu> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: warning message in standby |
| Date: | 2010-06-10 16:49:28 |
| Message-ID: | AANLkTiks4k9WqAZCMFH5Uq_xxC6u_NkkhS7PZY3ve9cF@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 10, 2010 at 5:13 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> At this point you should have a working HS/SR setup. Now:
>
> 8. shut the slave down
> 9. move recovery.conf out of the way
> 10. restart the slave - it will do recovery and enter normal running
> 11. make some database changes
> 12. stop the slave
> 13. put recovery.conf back
> 14. restart the slave
> 15. make a bunch of changes on the master
>
> When the slave then tries to replay, you then get something like:
>
> WARNING: invalid record length at 0/4005330
> WARNING: invalid record length at 0/4005330
> WARNING: invalid record length at 0/4005330
>
Woah, why does this procedure lead to this situation? I would hope
there's nothing a user could do which would cause it short of invoking
dd to corrupt the WAL files.
At precisely which step of the procedure did the user do something
wrong? Is there any reason we can't detect that they've done it and
throw a specific error message saying the configuration is invalid?
--
greg
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2010-06-10 16:54:17 | Re: warning message in standby |
| Previous Message | Josh Berkus | 2010-06-10 16:48:11 | Re: failover vs. read only queries |