Re: We've been affected by a pg_upgrade bug. What do we do next?

From: Shaun Thomas <sthomas(at)optionshouse(dot)com>
To: 'Alvaro Herrera' <alvherre(at)2ndquadrant(dot)com>
Cc: 'Andres Freund' <andres(at)2ndquadrant(dot)com>, 'Adrian Klaver' <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: We've been affected by a pg_upgrade bug. What do we do next?
Date: 2014-07-16 15:27:29
Message-ID: 0683F5F5A5C7FE419A752A034B4A0B9797AF6618@sswchi5pmbx2.peak6.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> It's an autovacuum worker, which is expected. Just get rid of the 0000
> file and all should be well.

That's what I figured, but I didn't want to make assumptions. Does removing the 0000 file require a restart?

______________________________________________

See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alvaro Herrera 2014-07-16 15:29:16 Re: We've been affected by a pg_upgrade bug. What do we do next?
Previous Message Alvaro Herrera 2014-07-16 15:22:54 Re: We've been affected by a pg_upgrade bug. What do we do next?