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

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Shaun Thomas <sthomas(at)optionshouse(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:30:36
Message-ID: 20140716153036.GI11811@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Shaun Thomas wrote:
>
> > 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?

Don't think so, but TBH I didn't try.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-general by date

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