| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | John R Pierce <pierce(at)hogranch(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgres DB is failed due to pg_Xlog is continues full. |
| Date: | 2017-09-14 03:59:24 |
| Message-ID: | CAB7nPqT0n92ssZoyVVCZ+jH-CkAX0TnSwQbnQkaCBqA_G9o5KA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Sep 14, 2017 at 12:44 PM, John R Pierce <pierce(at)hogranch(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yogesh Sharma | 2017-09-14 04:11:23 | Re: Postgres DB is failed due to pg_Xlog is continues full. |
| Previous Message | Yogesh Sharma | 2017-09-14 03:54:38 | Re: Postgres DB is failed due to pg_Xlog is continues full. |