| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Aidan Van Dyk <aidan(at)highrise(dot)ca>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL |
| Date: | 2010-03-25 13:43:53 |
| Message-ID: | 603c8f071003250643k123070f9ufd1dbfca40481c4f@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-docs pgsql-hackers |
On Thu, Mar 25, 2010 at 8:55 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> * If a corrupt WAL record is found in archive or streamed from master in
> standby mode, throw WARNING instead of PANIC, and keep trying. In
> archive recovery (ie. standby_mode=off) it's still a PANIC. We can make
> it a WARNING too, which gives the pre-9.0 behavior of starting up the
> server on corruption. I prefer PANIC but the discussion is still going on.
I don't think we should be changing pre-9.0 behavior more than necessary.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2010-03-25 14:44:34 | pgsql: Prevent ALTER USER f RESET ALL from removing the settings that |
| Previous Message | Heikki Linnakangas | 2010-03-25 12:55:42 | Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2010-03-25 19:45:22 | Re: [HACKERS] Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL |
| Previous Message | Heikki Linnakangas | 2010-03-25 12:55:42 | Re: Re: [COMMITTERS] pgsql: Make standby server continuously retry restoring the next WAL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2010-03-25 14:33:24 | Re: walreceiver is uninterruptible on win32 |
| Previous Message | chaoyong wang | 2010-03-25 13:00:38 | Access Violation when using Berkely DB in C-Language Function in VS2005 |