| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Excessive CPU usage in StandbyReleaseLocks() |
| Date: | 2018-06-19 14:45:04 |
| Message-ID: | CA+Tgmobfe=ExukJru2=E6k1Sp50DPg56YaNMQUyq=iqQco1POg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 19, 2018 at 2:30 AM, Andres Freund <andres(at)anarazel(dot)de> wrote:
> This should be a PANIC imo.
-1. As a developer, I would prefer PANIC. But as an end-user, I
would much rather have replay continue (with possible problems) than
have it stopped cold in its tracks with absolutely nothing that I as
the administrator can do to fix it. We should be building this
product for end users.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2018-06-19 14:50:39 | Re: WAL prefetch |
| Previous Message | Robert Haas | 2018-06-19 14:40:16 | Re: [bug fix] ECPG: freeing memory for pgtypes crashes on Windows |