Re: [ADMIN] postgres 8.2.9 transaction id wraparound failure

Maria L. Wilson wrote: > ouch!! ok - this may take me all week! > i'm opening each database when I start up the server ( postgres --single > -D /data/pg_devices /database1/ ) > i run the vacuum - just a plain old vacuum - nothing else... > i am getting output like this with each vacuum... Heh.

Re: [ADMIN] postgres 8.2.9 transaction id wraparound failure

sorry for the confusion - from what the docs - i am starting out the single user like this. postgres --single -D /data/pg_devices postgres *that connects me to the "postgres" database postgres --single -D /data/pg_devices n001acs *that connects me to the "n001acs" database... then I

Re: [ADMIN] postgres 8.2.9 transaction id wraparound failure

On Mon, Apr 20, 2009 at 1:43 PM, Maria L. Wilson wrote: > ouch!!  ok - this may take me all week! > i'm opening each database when I start up the server ( postgres --single -D > /data/pg_devices /database1/ ) is database1 the directory where you initialized the server? > i run the vacuum - just

Re: [ADMIN] postgres 8.2.9 transaction id wraparound failure

On Mon, Apr 20, 2009 at 12:43 PM, Maria L. Wilson wrote: > ouch!!  ok - this may take me all week! > i'm opening each database when I start up the server ( postgres --single -D > /data/pg_devices /database1/ ) This is not specifying the db to connect to. You need: postgres --single -D /data/pg_d

Re: [ADMIN] postgres 8.2.9 transaction id wraparound failure

ouch!! ok - this may take me all week! i'm opening each database when I start up the server ( postgres --single -D /data/pg_devices /database1/ ) i run the vacuum - just a plain old vacuum - nothing else... i am getting output like this with each vacuum... backend> [postg...@n116 ~]$ postgres

Re: [ADMIN] postgres 8.2.9 transaction id wraparound failure

Maria L. Wilson wrote: > I tried just vacuuming the "postgres" database first. No luck. Was > still unable to startup the server normally. Did the vacuum actually work? Note that you need to open the database you're going to vacuum, on the --single command line. > Here's is a snipped from th

Re: [ADMIN] postgres 8.2.9 transaction id wraparound failure

I tried just vacuuming the "postgres" database first. No luck. Was still unable to startup the server normally. Here's is a snipped from the query you suggested All the databases on this machine look similar. backend> SELECT datname, age(datfrozenxid) FROM pg_database ORDER BY age

Re: [ADMIN] postgres 8.2.9 transaction id wraparound failure

Maria L. Wilson wrote: > I was afraid you'd say that - any quick way to vacuum all 315 databases > on this machine? Actually you only need to vacuum the database being complained about -- "postgres" in this case. You can issue SELECT datname, age(datfrozenxid) FROM pg_database ORDER BY age(datf

Re: [ADMIN] postgres 8.2.9 transaction id wraparound failure

I was afraid you'd say that - any quick way to vacuum all 315 databases on this machine? thanks.. Joshua D. Drake wrote: On Mon, 2009-04-20 at 13:49 -0400, Maria L. Wilson wrote: running on a linux box i've inherited this test machine getting the following errors in the logs sco

Re: [ADMIN] postgres 8.2.9 transaction id wraparound failure

On Mon, 2009-04-20 at 13:49 -0400, Maria L. Wilson wrote: > running on a linux box > > i've inherited this test machine getting the following errors in the > logs > > scoogan 198.119.134.228 2009-04-20 11:42:48.762 EDT 0 [9181] > [scoogan_ange_1.2] FATAL: database is not accepting commands

[ADMIN] postgres 8.2.9 transaction id wraparound failure

running on a linux box i've inherited this test machine getting the following errors in the logs scoogan 198.119.134.228 2009-04-20 11:42:48.762 EDT 0 [9181] [scoogan_ange_1.2] FATAL: database is not accepting commands to avoid wraparound data loss in database "postgres" scoogan 198.119