| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgresql General <pgsql-general(at)postgresql(dot)org>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Subject: | Re: startup process stuck in recovery |
| Date: | 2017-10-11 07:09:23 |
| Message-ID: | 17DBC10C-3F8E-4CB5-87B5-A7418DF65A7F@thebuild.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Oct 10, 2017, at 23:54, Simon Riggs <simon(at)2ndQuadrant(dot)com> wrote:
>
> The use case described seems incredibly
> unreal and certainly amenable to being rewritten.
While it's certainly true that this was an extreme case, it was a real-life production situation. The concern here is that in the actual production situation, the only symptom was that the startup process just stopped. There were no log messages or any other indication of what was going wrong.
--
-- Christophe Pettus
xof(at)thebuild(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2017-10-11 07:41:58 | Why does increasing the precision of a numeric column rewrites the table? |
| Previous Message | Simon Riggs | 2017-10-11 06:54:32 | Re: startup process stuck in recovery |