| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FSM corruption leading to errors |
| Date: | 2016-10-24 03:59:18 |
| Message-ID: | CAB7nPqTOfWKiqpJdPaoHg27+Svsds487Ycx9whxoN3kbggTFTQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Oct 22, 2016 at 7:31 AM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> On Sat, Oct 22, 2016 at 5:17 AM, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com> wrote:
>> On 10/20/16 10:15 PM, Michael Paquier wrote:
>>>
>>> 2) If anything is found, stop the server and delete the files manually.
>>> 3) Re-start the server.
>>> OK, that's troublesome and costly for large relations, but we know
>>> that's the safest way to go for any versions, and there is no need to
>>> complicate the code with any one-time repairing extensions.
>>
>> Wouldn't you need to run around to all your replicas and do that as well?
>
> Yeah...
Release notes refer to this page for methods to fix corrupted instances:
https://wiki.postgresql.org/wiki/Free_Space_Map_Problems
I just typed something based on Pavan's upper method, feel free to
jump in and improve it as necessary.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2016-10-24 04:26:37 | Re: [BUG] pg_basebackup from disconnected standby fails |
| Previous Message | Kyotaro HORIGUCHI | 2016-10-24 03:48:02 | Re: [BUG] pg_basebackup from disconnected standby fails |