From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | djlopes(at)gmail(dot)com |
Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #14440: Error starting postgres |
Date: | 2016-11-29 23:57:47 |
Message-ID: | CAKFQuwYRUX_0fLz9uaXmSgbn_BdX42vRXUfEG=+cpeUuaW_-mw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Nov 29, 2016 at 4:28 PM, <djlopes(at)gmail(dot)com> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 14440
>
> 2016-11-29 23:27:17 WET LOG: database system was interrupted while in
> recovery at 2016-11-29 22:06:46 WET
> 2016-11-29 23:27:17 WET HINT: This probably means that some data is
> corrupted and you will have to use the last backup for recovery.
>
Without any commentary on your part I'm going to say that this is not a
bug but rather, as the hint suggests, data corruption.
If you wish to discuss PostgreSQL administration it would be customary to
subscribe to the pgsql-general list and post some background and questions
there. The bug reporting mechanism is not a proper forum for such a
discussion.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-11-30 00:01:16 | Re: parallel sequential scan returns extraneous rows |
Previous Message | djlopes | 2016-11-29 23:28:32 | BUG #14440: Error starting postgres |