Rural Hunter wrote > I'm on 9.2.4 and I have several databases on the instance say db1, db2, > db2 etc. Today I got this error message on connection of any of the > databases: > ERROR: database is not accepting commands to avoid wraparound data loss > in database "db1" > Suggestion：Stop the postmaster and use a standalone backend to > vacuum that database. > > The error messages says problem is on db1 when I connected to any > database. But after I did vacuum full on some other databases such as db2, > db2, but not db1, the problem disappeared. > Was that just a wrong database name in the error message? Likely auto-vacuum kicked in and took care of the wraparound issue while the system was handling your manual vacuum routines...but that is just a theory David J. -- View this message in context: http://postgresql.1045698.n5.nabble.com/wrong-database-name-in-error-message-tp5770815p5770822.html Sent from the PostgreSQL - admin mailing list archive at Nabble.com. -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
