X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.192]) by svr1.postgresql.org (Postfix) with ESMTP id 47CE4CC409; Tue, 15 Jul 2003 16:26:04 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr4.postgresql.org [64.117.224.192]) (amavisd-new, port 10024) with ESMTP id 30270-07; Tue, 15 Jul 2003 16:26:31 +0000 (GMT) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 13A18CC419; Tue, 15 Jul 2003 13:26:02 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.9/8.12.9) with ESMTP id h6FGQTQ3023212; Tue, 15 Jul 2003 12:26:29 -0400 (EDT) To: "Kuhn, Dylan K (4520500D)" Cc: pgsql-admin@postgresql.org, pgsql-hackers@postgresql.org Subject: Re: problems with pg_restore In-reply-to: <78ED1F30F0D85B4698FBD6CF2A5AC8F5A576F9@NAWECHLKEX01VA.nadsuswe.nads.navy.mil> References: <78ED1F30F0D85B4698FBD6CF2A5AC8F5A576F9@NAWECHLKEX01VA.nadsuswe.nads.navy.mil> Comments: In-reply-to "Kuhn, Dylan K (4520500D)" message dated "Tue, 15 Jul 2003 07:55:21 -0700" Date: Tue, 15 Jul 2003 12:26:29 -0400 Message-ID: <23211.1058286389@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200307/137 X-Sequence-Number: 9477 "Kuhn, Dylan K (4520500D)" writes: > [ tries to restore a dump into a database with a different name ] > pg_restore: [archiver (db)] could not execute query: ERROR: Database commen= > ts may only be applied to the current database > I'm not sure how to get around this one. Can an archived database with com= > ments be restored to a database with a different name? Hm. Evidently not :-(. The COMMENT ON DATABASE facility is a bit bogus anyway (since there's no way to make the comments visible across databases). You might be best advised not to use it. Hackers: this seems like an extremely bad side-effect of what we thought was a simple addition of a helpful check. I am thinking we should either remove the check again, or downgrade it to a WARNING (though I'm not quite sure how to phrase the warning ...). Any thoughts? regards, tom lane