Received: from malur.postgresql.org ([217.196.149.56])
 by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M41616=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1VKeaQ-0008Cv-5N
 for pgsql-admin@arkaria.postgresql.org; Sat, 14 Sep 2013 01:23:46 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
 by malur.postgresql.org with smtp (Exim 4.80) (envelope-from
 <pgsql-admin-owner+M41616=pgsql+2Dadmin=arkaria.postgresql.org@postgresql.org>)
 id 1VKeaP-0006kD-Ci
 for pgsql-admin@arkaria.postgresql.org; Sat, 14 Sep 2013 01:23:45 +0000
Received: from makus.postgresql.org ([2001:4800:7903:4::125])
 by malur.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <ruralhunter@gmail.com>) id 1VKeaN-0006k4-76
 for pgsql-admin@postgresql.org; Sat, 14 Sep 2013 01:23:43 +0000
Received: from mail-pd0-x233.google.com ([2607:f8b0:400e:c02::233])
 by makus.postgresql.org with esmtp (Exim 4.80)
 (envelope-from <ruralhunter@gmail.com>) id 1VKeaJ-00010a-DF
 for pgsql-admin@postgresql.org; Sat, 14 Sep 2013 01:23:41 +0000
Received: by mail-pd0-f179.google.com with SMTP id v10so1921596pde.24
 for <pgsql-admin@postgresql.org>; Fri, 13 Sep 2013 18:23:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=message-id:date:from:user-agent:mime-version:to:subject
 :content-type:content-transfer-encoding;
 bh=3sx8KsbPSQWS97gXACwv3JhrnPtXAdG2NaOS+yrH+R0=;
 b=VirlZbpigEYLjNH59Rg+Yfl8vn2hHKfy2V7WfeY/wVvzTr1+KGEtlVJ4okIC0BKhNU
 zKropdEC6t6215NJ+OftFARiIA5449XvnlToO5vyL0zVsvPIJGi6MQC4QaN/nvpm3OGa
 SK1x25GgO/qc9o0ZZnaLusB5RlglOzhSyzDtimdXLUBhcoCK54p/1+ppd3WbZ7Ok/wii
 OoZakT1H50kglO0WljGLpIR1pCmJXexqR34dplpRKNZ98uzxlxkMvp6IMDcP9xu3cvmE
 xIjZ/KrGBiwZGDJF7/YryO2GNFw04Rhz/WS+qOfjvancHVG+YDcS3lkecs//GylUKbDE
 UNqA==
X-Received: by 10.68.129.201 with SMTP id ny9mr16631922pbb.70.1379121817036;
 Fri, 13 Sep 2013 18:23:37 -0700 (PDT)
Received: from [192.168.11.3] ([180.164.128.119])
 by mx.google.com with ESMTPSA id vz4sm21266478pab.11.1969.12.31.16.00.00
 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
 Fri, 13 Sep 2013 18:23:36 -0700 (PDT)
Message-ID: <5233BA90.3020107@gmail.com>
Date: Sat, 14 Sep 2013 09:23:28 +0800
From: Rural Hunter <ruralhunter@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1;
 rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: pgsql-admin@postgresql.org
Subject: wrong database name in error message?
Content-Type: text/plain; charset=GB18030; format=flowed
Content-Transfer-Encoding: 8bit
X-Pg-Spam-Score: 0.7 (/)
List-Archive: <http://archives.postgresql.org/pgsql-admin>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-admin.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@postgresql.org>
List-Post: <mailto:pgsql-admin@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-admin>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
X-Mailing-List: pgsql-admin
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

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?



-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin