Re: [GENERAL] Postgres DB is failed due to pg_Xlog is continues full.
| От | Michael Paquier |
|---|---|
| Тема | Re: [GENERAL] Postgres DB is failed due to pg_Xlog is continues full. |
| Дата | |
| Msg-id | CAB7nPqT0n92ssZoyVVCZ+jH-CkAX0TnSwQbnQkaCBqA_G9o5KA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [GENERAL] Postgres DB is failed due to pg_Xlog is continues full. (John R Pierce <pierce@hogranch.com>) |
| Ответы |
Re: [GENERAL] Postgres DB is failed due to pg_Xlog is continues full.
|
| Список | pgsql-general |
On Thu, Sep 14, 2017 at 12:44 PM, John R Pierce <pierce@hogranch.com> wrote: > prior to that error, something else catastrophic must have happened to the > system, that error is more of a side effect. recovering a database server > that far gone which is running such an obsolete version will likely be an > expensive proposition. before doing anything, you should make a complete > backup of the $PGDATA directory (and other tablespace directories, if you > use any). Definitely take a backup of PGDATA before doing anything! What you could do is copying its contents to a large disk, and then allow it to recover from the crash. You are going to need more space at the end. And yes, upgrade as well. Lagging 7 major releases behind cannot be an excuse. -- Michael -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: