| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | vinod kale <vinod16895(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Block corruption Error. |
| Date: | 2020-06-04 14:49:59 |
| Message-ID: | CAMkU=1xqJUG3k9rBY_GfTMt5aw58o7QY5qW+n8D=zen26fwjSg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
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 | MichaelDBA@sqlexec.com | 2020-06-04 15:11:37 | Re: Block corruption Error. |
| Previous Message | Mat Hanson | 2020-06-04 07:03:46 | LDAPS Connection Issue - Unable to open socket |