Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VKfY1-0003rO-GZ for pgsql-admin@arkaria.postgresql.org; Sat, 14 Sep 2013 02:25:21 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1VKfY0-0002g9-Rk for pgsql-admin@arkaria.postgresql.org; Sat, 14 Sep 2013 02:25:20 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VKfXz-0002g2-Nq for pgsql-admin@postgresql.org; Sat, 14 Sep 2013 02:25:19 +0000 Received: from sam.nabble.com ([216.139.236.26]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1VKfXx-00026K-0j for pgsql-admin@postgresql.org; Sat, 14 Sep 2013 02:25:19 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1VKfXv-0007EW-An for pgsql-admin@postgresql.org; Fri, 13 Sep 2013 19:25:15 -0700 Date: Fri, 13 Sep 2013 19:25:15 -0700 (PDT) From: David Johnston To: pgsql-admin@postgresql.org Message-ID: <1379125515329-5770822.post@n5.nabble.com> In-Reply-To: <5233BA90.3020107@gmail.com> References: <5233BA90.3020107@gmail.com> Subject: Re: wrong database name in error message? MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Pg-Spam-Score: 4.5 (++++) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Rural Hunter wrote > I'm on 9.2.4 and I have several databases on the instance say db1, db2,=20 > db2 etc. Today I got this error message on connection of any of the=20 > databases: > ERROR: database is not accepting commands to avoid wraparound data loss=20 > in database "db1" > Suggestion=EF=BC=9AStop the postmaster and use a standalone backend to= =20 > vacuum that database. >=20 > 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. --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin