| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, 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-14 14:43:38 |
| Message-ID: | AANLkTinVYmnlC_FyOvUCTx1wvVYIX_WEyDlZTI7S4NAG@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jun 14, 2010 at 10:38 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> I'm willing to buy the above, but nobody has explained to my
>> satisfaction why it's remotely sane to go into an infinite retry loop
>> on an unrecoverable error.
>
> That's a different question altogether ;-). I assume you're not
> satisfied by the change Heikki committed a couple hours ago?
> It will at least try to do something to recover.
Yeah, I'm not satisfied by that. It's an improvement in the technical
sense - it replaces an infinite retry that spins at top speed with a
slower retry that won't flog your CPU quite so badly, but the chances
that it will actually succeed in correcting the underlying problem
seem infinitesimal.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Sabino Mullane | 2010-06-14 14:55:44 | Re: Typo in plperl doc ? |
| Previous Message | Tom Lane | 2010-06-14 14:38:08 | Re: warning message in standby |