From: Rod Taylor <rbt@rbt.ca>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Kuhn, Dylan K (4520500D) <Dylan.Kuhn@navy.mil>
Cc: pgsql-admin@postgresql.org, PostgreSQL Development <pgsql-hackers@postgresql.org>
Subject: Re: problems with pg_restore
Date: 15 Jul 2003 19:50:51 +0000
Message-ID: <1058298650.9981.117.camel@jester> (raw)
In-Reply-To: <23211.1058286389@sss.pgh.pa.us>
References: <78ED1F30F0D85B4698FBD6CF2A5AC8F5A576F9@NAWECHLKEX01VA.nadsuswe.nads.navy.mil>
<23211.1058286389@sss.pgh.pa.us>
> 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?
How about going the other way and removing the requirement to explicitly
state the database?
COMMENT ON DATABASE IS 'This comment is on the current database.';
Attachments:
signature.asc (application/pgp-signature, 186B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: rbt@rbt.ca, tgl@sss.pgh.pa.us, Dylan.Kuhn@navy.mil, pgsql-hackers@postgresql.org
Subject: Re: problems with pg_restore
In-Reply-To: <1058298650.9981.117.camel@jester>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox