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
Date: Wed, 08 Feb 2017 11:13:47 -0500
Message-ID: <2262.1486570427@sss.pgh.pa.us> (raw)
In-Reply-To: <DM5PR07MB274739313B295419FA607B9E86420@DM5PR07MB2747.namprd07.prod.outlook.com>
References: <DM5PR07MB274739313B295419FA607B9E86420@DM5PR07MB2747.namprd07.prod.outlook.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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=,db=,app=,client= WARNING: database "db1" must be vacuumed within 999999 transactions
> 2017-02-07 23:25:15 EST [54045]: [9-1] user=,db=,app=,client= HINT: To avoid a database shutdown, execute a database-wide VACUUM in that database.
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
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, ganesh.kannan@weatheranalytics.com
Subject: Re: Recovery from Transaction wraparound failure
In-Reply-To: <2262.1486570427@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox