| From: | Yogesh Sharma <yogeshraj95(at)gmail(dot)com> |
|---|---|
| To: | Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Postgres DB is failed due to pg_Xlog is continues full. |
| Date: | 2017-09-14 03:54:38 |
| Message-ID: | CAEZUwCTsFk1wPU0AAx-LgfGwagsWH-js_jHGhtO03EO4t2BL3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Dear all,
As current situation, i can not upgrade on higher version.
Is there any recovery command available?
Regards,
Yogesh
On Thursday, September 14, 2017, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
wrote:
> On 14/09/17 15:29, Yogesh Sharma wrote:
>
>> Dear All,
>>
>> Thanks in advance.
>>
>> We are using Postgres 8.1.18 version.
>> In Postgres log, we found below logs.
>> –---------------------
>> CONTEXT:writing block 0 of relation 1664/0/1260
>> ERROR: could not write block 0 of relation 1664/0/1260: Bad address
>>
>> ------------------------
>> Due to this pglog_Xlog directory has been continuously increased and
>> directory has been full and Postgres is stopped.
>> Please let me know how to recover this issue.
>>
>> Regards.
>> Yogesh
>>
>
> When you have recovered from that - I strong suggest that you consider
> upgrading to a supported version of Postgres like 9.6.5, as Postgres 8 is
> no longer supported and later versions have many bug fixes and
> enhancements! Note that Postgres will be released in a few weeks.
>
>
> Cheers,
> Gavin
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-09-14 03:59:24 | Re: Postgres DB is failed due to pg_Xlog is continues full. |
| Previous Message | John R Pierce | 2017-09-14 03:44:39 | Re: Postgres DB is failed due to pg_Xlog is continues full. |