Postgres Pro
Downloads
Home   >   mailing lists

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

From Shaun Thomas
Subject Re: We've been affected by a pg_upgrade bug. What do we do next?
Date
Msg-id 0683F5F5A5C7FE419A752A034B4A0B9797AF6618@sswchi5pmbx2.peak6.net
Whole thread Raw
In response to Re: We've been affected by a pg_upgrade bug. What do we do next?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: We've been affected by a pg_upgrade bug. What do we do next?  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-general
Tree view 
> 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

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: We've been affected by a pg_upgrade bug. What do we do next?
Next
From: Alvaro Herrera
Date:
Subject: Re: We've been affected by a pg_upgrade bug. What do we do next?