Re: We've been affected by a pg_upgrade bug. What do we do next? - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: We've been affected by a pg_upgrade bug. What do we do next?
Date
Msg-id 20140716153036.GI11811@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: We've been affected by a pg_upgrade bug. What do we do next?  (Shaun Thomas <sthomas@optionshouse.com>)
List 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


pgsql-general by date:

Previous
From: Shaun Thomas
Date:
Subject: Re: We've been affected by a pg_upgrade bug. What do we do next?
Next
From: jlliu
Date:
Subject: Why pg_toast table not get auto vacuumed?