On 14/09/17 16:11, Yogesh Sharma wrote:
>>What you could do is copying its contents to a large disk, and then
allow it to recover from the crash.
I will copy the PGDATA into large disk. After that it is require to
execute some specific command or automatically recovery will start?
If any comma
On 9/13/2017 9:11 PM, Yogesh Sharma wrote:
>>What you could do is copying its contents to a large disk, and then
allow it to recover from the crash.
I will copy the PGDATA into large disk. After that it is require to
execute some specific command or automatically recovery will start?
If any co
>>What you could do is copying its contents to a large disk, and then allow
it to recover from the crash.
I will copy the PGDATA into large disk. After that it is require to
execute some specific command or automatically recovery will start?
If any command is require to execute please let me know.
On Thu, Sep 14, 2017 at 12:44 PM, John R Pierce 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 pr
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
wrote:
> On 14/09/17 15:29, Yogesh Sharma wrote:
>
>> Dear All,
>>
>> Thanks in advance.
>>
>> We are using Postgres 8.1.
On 9/13/2017 8:29 PM, Yogesh Sharma wrote:
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
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
--
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 dire