From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ganesh Kannan <ganesh.kannan@weatheranalytics.com>
cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: Recovery from Transaction wraparound failure
In-reply-to: 
 <DM5PR07MB274739313B295419FA607B9E86420@DM5PR07MB2747.namprd07.prod.outlook.com>
References: 
 <DM5PR07MB274739313B295419FA607B9E86420@DM5PR07MB2747.namprd07.prod.outlook.com>
Comments: In-reply-to Ganesh Kannan <ganesh.kannan@weatheranalytics.com>
	message dated "Wed, 08 Feb 2017 06:48:10 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <2261.1486570427.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 08 Feb 2017 11:13:47 -0500
Message-ID: <2262.1486570427@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Ganesh Kannan <ganesh.kannan@weatheranalytics.com> writes:
> 1) After reading the documentation, I thought I could try to vacuum
> those 20 tables that were never vacuumed individually ( with relfrozenid
> more than 2 billion) in single-user mode, but it is not working (error
> copied below).

That is not an error, it's just a warning:

> backend>  vacuum freeze schema.wd_p51_y2015;
> 2017-02-07 23:25:15 EST [54045]: [8-1] user=3D,db=3D,app=3D,client=3D WAR=
NING:  database "db1" must be vacuumed within 999999 transactions
> 2017-02-07 23:25:15 EST [54045]: [9-1] user=3D,db=3D,app=3D,client=3D HIN=
T:  To avoid a database shutdown, execute a database-wide VACUUM in that da=
tabase.

It's telling you that you haven't finished fixing the problem, not that
this command didn't do anything.

> Is there a way to do vacuum of individual tables in
> single-user mode?

You're doing it.  I don't think you really need the "freeze" modifier
though, and that may be forcing more I/O than is needed to get out of
trouble.

			regards, tom lane


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin