Re: [ADMIN] pg_upgrade from 9.1.3 to 9.2 failed
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rural Hunter <ruralhunter@gmail.com>
Cc: Bruce Momjian <bruce@momjian.us>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2012-09-17T03:07:44Z
Lists: pgsql-hackers
Rural Hunter <ruralhunter@gmail.com> writes: > 2012917 9:48:58,Tom Lane: >> I wonder whether you dropped and recreated the information_schema in >> the lifetime of this database? We have recommended doing that in the >> past, IIRC. Could such a thing have confused pg_dump? > No, I have never manually re-created the table. I think you must have, because the query output shows that sql_features, its rowtype, and the information_schema all have OIDs much larger than they would have had in a virgin installation. The large relfilenode could have been explained by a VACUUM FULL, but the other OIDs wouldn't have been changed by that. > This is the first time > I see the name. But I'm not sure other things I installed before > recreated it or not, such as pg_buffercache etc. One more thing, is > this a hidden table? I can see it with '\d > information_schema.sql_features' but it's not in the list of '\d'. That just means that information_schema is not in your search_path. 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