Received: from magus.postgresql.org ([87.238.57.229]) by malur.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TDTYR-00062R-K0 for pgsql-hackers@postgresql.org; Mon, 17 Sep 2012 05:07:31 +0000 Received: from mail-pb0-f46.google.com ([209.85.160.46]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1TDTYP-0003ka-91 for pgsql-hackers@postgresql.org; Mon, 17 Sep 2012 05:07:31 +0000 Received: by pbbrr13 with SMTP id rr13so8457345pbb.19 for ; Sun, 16 Sep 2012 22:07:27 -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:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=/eymeXGCIWtMD7sr5doTpy9hB+RFhwDsv6h+oV3zb3c=; b=xZaNcMQEDzCv6VQdOkLQ95doRYrXwNz4/14x28kjTxkqT3dV+E6J9wCYocVwCilHhh szCTm+BE8viJcJqu2tW7MGRSOuOVyNCobxgWGerJ+hAbg1tF5cw1QPrsu7c93eJPfM+9 OEvC0xcbiWZsIdOmIsR9hcZ3OuNcST1I/n3kcqloAQLtQjl/i1ZlkjG3CVL2aS0juFE7 RJ88MMOAsPWWbWJNo8jb+MmqjUCyajQDFOXy68vm4bexNVA9+30rztNZguzAdLzhpZWf TGkzEyTOJv68xrksj0my8n4dUlqx2SN57PBHv0nbODF6XVTO38aaEmeZOpDXhRK5opxw Uiig== Received: by 10.68.229.201 with SMTP id ss9mr218351pbc.80.1347858447908; Sun, 16 Sep 2012 22:07:27 -0700 (PDT) Received: from [192.168.1.7] ([116.226.32.153]) by mx.google.com with ESMTPS id pn4sm6336618pbb.50.2012.09.16.22.07.24 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 16 Sep 2012 22:07:26 -0700 (PDT) Message-ID: <5056B008.4010209@gmail.com> Date: Mon, 17 Sep 2012 13:07:20 +0800 From: Rural Hunter User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20120907 Thunderbird/15.0.1 MIME-Version: 1.0 To: Tom Lane CC: PostgreSQL-development , Bruce Momjian Subject: Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed References: <5052C402.8020003@gmail.com> <20120914142616.GA11265@momjian.us> <50535302.8080000@gmail.com> <20120914183915.GA5933@momjian.us> <5053F896.60005@gmail.com> <20120915180603.GA20907@momjian.us> <505557CD.8090304@gmail.com> <20120916171746.GA24907@momjian.us> <50567E60.2000005@gmail.com> <2932.1347846538@sss.pgh.pa.us> <20120917043500.GB20123@momjian.us> <6578.1347857231@sss.pgh.pa.us> In-Reply-To: <6578.1347857231@sss.pgh.pa.us> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.7 (--) X-Archive-Number: 201209/633 X-Sequence-Number: 213661 于2012年9月17日 12:47:11,Tom Lane写到: > Bruce Momjian writes: >> On Sun, Sep 16, 2012 at 09:48:58PM -0400, Tom Lane wrote: >>> Well, that's even stranger, because (1) information_schema.sql_features >>> ought to have a toast table in either version, and (2) neither pg_dump >>> nor pg_upgrade ought to be attempting to dump or transfer that table. > >> I bet pg_upgrade is picking it up from the old cluster because it has an >> oid >= FirstNormalObjectId and the table is not in the information >> schema. > > If it *isn't* in information_schema, but is just some random table that > happens to be named sql_features, then it's hard to explain why there's > anything going wrong at all. My money is on the OP having done a reload > of the information_schema (as per, eg, the release notes for 9.1.2), and > somehow that's confusing pg_dump and/or pg_upgrade. ah yes yes, now I can remember it! I have followed the release notes and re-created the whole information_schema schema. > > regards, tom lane >