From: | "MichaelDBA(at)sqlexec(dot)com" <michaeldba(at)sqlexec(dot)com> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | vinod kale <vinod16895(at)gmail(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Block corruption Error. |
Date: | 2020-06-04 15:11:37 |
Message-ID: | A4156F26-6BAA-4C34-B913-6EC8F58CF8EC@sqlexec.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Loop thru the affected tables using primary key or ctid and catch exception rows and delete them
Sent from my iPhone
> On Jun 4, 2020, at 10:50 AM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>
>
>> On Tue, Jun 2, 2020 at 11:11 AM vinod kale <vinod16895(at)gmail(dot)com> wrote:
>
>> Hello Team,
>>
>> We have generated one scenario for learning purpose regarding block corruption.
>> We have manually corrupt the one table file at disk level and after queried to that table we got below attached error.
>> So could you please help me out in below scenario?
>> What is the best method to resolve below error. ?
>
> I don't understand what you are asking. You intentionally created corruption, so now you have corruption. Restore from a backup plus archived WAL files, or promote your standby, or do whatever your recovery plan dictates.
>
> Of course you could just edit the file and reverse whatever it is you did (while the db is shutdown), but that would not constitute a plan.
>
> Cheers,
>
> Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Vivek Gadge | 2020-06-06 18:24:20 | PostgreSQL Concern Regarding PITR. |
Previous Message | Jeff Janes | 2020-06-04 14:49:59 | Re: Block corruption Error. |