From: | Matthew O'Connor <matthew(at)zeut(dot)net> |
---|---|
To: | Sriram Dandapani <sdandapani(at)counterpane(dot)com> |
Cc: | 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-06 17:25:51 |
Message-ID: | 44FF049F.8050709@zeut.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
A PostgreSQL superuser, so yes user postgres will work just fine.
Sriram Dandapani wrote:
> Do you mean that I login as say root and issue a vacuumdb (or do I login
> as a postgres user with special privileges)
>
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Wednesday, September 06, 2006 6:41 AM
> To: Sriram Dandapani
> Cc: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] transactoin id wraparound problem
>
> "Sriram Dandapani" <sdandapani(at)counterpane(dot)com> writes:
>> I get error messages on the console that says
>> WARNING: database "xxx" must be vacuumed within 10094646 transactions
>
>> I shutdown, restart pg and issue a vacuumdb -f <database>
>
> The shutdown/restart was a waste of typing, and -f doesn't really help
> here either.
>
>> I still get messages saying database must be vacuumed and the
>> transaction count keeps decreasing.
>
> I'll bet a nickel you did not run the vacuum as superuser. It has to be
> done by a superuser to have permission to vacuum every table in the
> database (including system catalogs).
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Sullivan | 2006-09-06 17:31:02 | Re: transactoin id wraparound problem |
Previous Message | Sriram Dandapani | 2006-09-06 16:48:45 | Re: transactoin id wraparound problem |