| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Vijaykumar Jain <vijaykumarjain(dot)github(at)gmail(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Data corruption |
| Date: | 2021-07-21 17:09:07 |
| Message-ID: | 17C82666-5695-4AD0-AA82-5B4BA9E256A4@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Do you have any clue as to how this happened?
If you have a hardware problem, disk, controller or cable that is corrupting data written, then any efforts you make at recovery on the same hardware could just result in more & more corruption.
You don't mention, I think, whether you've copied the data to different storage (and preferably different server), but if you haven't already done so, STOP RIGHT NOW and do nothing else with this db until you've done that.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin Struckhoff | 2021-07-21 17:57:44 | Re: Postgres 13.3 times out when attempting to connect via odbc & pgAdmin4 |
| Previous Message | soumitra bhandary | 2021-07-21 17:03:23 | Re: Data corruption |