On Mon, Mar 4, 2013 at 6:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Magnus Hagander <magnus@hagander.net> writes:
>> On Mon, Mar 4, 2013 at 4:48 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> Being a paranoid sort, I'm doing a full new "git clone" to compare
>>> to my old repo. But assuming that that's okay, what instructions
>>> do you want to give committers about recovering? There should be
>>> a followup with that info to the pgsql-hackers message you posted.
>
>> Yes, please do that comparison. Alvaro looked it over and found things
>> to look right, but one more paranoid check would be very good.
>
> AFAICT things are okay now.
Great. I'll "release" in the other thread then.
> One thing that would be interesting to try is to look for commits that
> are unreachable from any of the branch heads, to verify that we've
> not missed anything else. I imagine git has a command for that, but
> I don't know it --- any ideas?
I'm running the fsck command suggested by Andres. It's taking a long
time to run, but I'll report if it finds something we shouldn't have.
-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/
