From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Ganesh Kannan <ganesh(dot)kannan(at)weatheranalytics(dot)com> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Recovery from Transaction wraparound failure |
Date: | 2017-02-08 16:13:47 |
Message-ID: | 2262.1486570427@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Ganesh Kannan <ganesh(dot)kannan(at)weatheranalytics(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Lazaro Garcia | 2017-02-08 16:27:42 | Why pgpool TPS is lowest versus postgresql direct connections? |
Previous Message | Ganesh Kannan | 2017-02-08 15:28:51 | Re: Recovery from Transaction wraparound failure |