On Sat, Oct 22, 2016 at 7:31 AM, Michael Paquier <michael.paqu...@gmail.com> wrote: > On Sat, Oct 22, 2016 at 5:17 AM, Jim Nasby <jim.na...@bluetreble.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
