| From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
|---|---|
| To: | marc47marc47(at)gmail(dot)com |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14143: stop database with -m immediate cause fatal message log when database start |
| Date: | 2016-05-17 11:23:51 |
| Message-ID: | CACjxUsPQCm+ub0XssNcMWJquM4HohxhXwBRhe=bbFUKx23W0Nw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, May 17, 2016 at 12:14 AM, <marc47marc47(at)gmail(dot)com> wrote:
> The database start with FATAL message when I try to stop the database with
> immediate.
That is not a bug; stop immediate forces a crash of the service, and
crash recovery is needed when the service is started again.
> I assume that FATAL, is a critical error log, it should be an warning
> only.
FATAL means the connection involved was broken. It was. More than
that, though, you should pretty much never use stop immediate unless
the building is on fire (literally) or you don't plan to keep the
cluster after it is stopped.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | door | 2016-05-17 14:43:53 | BUG #14144: 8.4 version no longer available |
| Previous Message | marc47marc47 | 2016-05-17 04:14:28 | BUG #14143: stop database with -m immediate cause fatal message log when database start |