Re: Block corruption Error.
| От | MichaelDBA@sqlexec.com |
|---|---|
| Тема | Re: Block corruption Error. |
| Дата | |
| Msg-id | A4156F26-6BAA-4C34-B913-6EC8F58CF8EC@sqlexec.com обсуждение исходный текст |
| Ответ на | Re: Block corruption Error. (Jeff Janes <jeff.janes@gmail.com>) |
| Список | 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.janes@gmail.com> wrote:
On Tue, Jun 2, 2020 at 11:11 AM vinod kale <vinod16895@gmail.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
В списке pgsql-admin по дате отправления: