Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
Rural Hunter <ruralhunter@gmail.com>
From: Rural Hunter <ruralhunter@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>, Bruce Momjian <bruce@momjian.us>
Date: 2012-09-17T05:07:20Z
Lists: pgsql-hackers
于2012年9月17日 12:47:11,Tom Lane写到: > Bruce Momjian <bruce@momjian.us> 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 >
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Replace empty locale name with implied value in CREATE DATABASE and initdb.
- c7cea267de3c 9.2.0 cited