Re: transactoin id wraparound problem

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Sriram Dandapani <sdandapani(at)counterpane(dot)com>
Cc: Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-admin(at)postgresql(dot)org
Subject: Re: transactoin id wraparound problem
Date: 2006-09-07 02:47:50
Message-ID: 20060907024750.GN14024@alvh.no-ip.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Sriram Dandapani wrote:
> Hi
> I have several such databases to issue vacuum on. If I were to vacuum
> each table individually, would the transaction id be updated after every
> table vacuum.

No, you must issue database-wide vacuums. Single-table vacuums, even if
done to each and every table, do not suffice.

> Wonder if it is because I have several large partitioned tables that I
> drop every day that don't get vacuumed enough.

The best time of the day to do the vacuum would be just after one such
partition was dropped, one would think.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Iuri Sampaio 2006-09-07 05:56:46 psql command
Previous Message Sriram Dandapani 2006-09-06 23:32:15 Re: transactoin id wraparound problem