Message-ID: <5237ACDA.8070006@gmail.com>
Date: Tue, 17 Sep 2013 09:14:02 +0800
From: Rural Hunter <ruralhunter@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Kevin Grittner <kgrittn@ymail.com>
CC: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: wrong database name in error message?
References: <5233BA90.3020107@gmail.com>
 <20130914045519.GD5033@eldon.alvh.no-ip.org> <5233F3A9.30901@gmail.com>
 <1379178368.98727.YahooMailNeo@web162901.mail.bf1.yahoo.com>
 <523507DE.3060909@gmail.com>
 <1379266279.54874.YahooMailNeo@web162902.mail.bf1.yahoo.com>
 <52366022.8020706@gmail.com>
 <1379347372.27022.YahooMailNeo@web162906.mail.bf1.yahoo.com>
In-Reply-To: <1379347372.27022.YahooMailNeo@web162906.mail.bf1.yahoo.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

于 2013/9/17 0:02, Kevin Grittner 写道:
> Possibly. As I said before, I think the symptoms might better fit a 
> situation where the table in need of VACUUM was a shared table and it 
> just happened to mention db1 because that was the database it was 
> scanning at the time. (Every database includes the shared system 
> tables in its catalog.)
OK, that sounds reasonable. thanks a lot for your advice and explanation.


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