pgsql: Update COMMENT item: < o Prevent COMMENT ON dbname from issuing - Mailing list pgsql-committers

From momjian@postgresql.org (Bruce Momjian)
Subject pgsql: Update COMMENT item: < o Prevent COMMENT ON dbname from issuing
Date
Msg-id 20071120001846.810347540F0@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Update COMMENT item:

<     o Prevent COMMENT ON dbname from issuing a warning when loading
<       into a database with a different name, perhaps using COMMENT ON
<       CURRENT DATABASE
>     o Change pg_dump so that a comment on the dumped database is
>       applied to the loaded database, even if the database has a
>       different name.  This will require new backend syntax, perhaps
>       COMMENT ON CURRENT DATABASE.

Modified Files:
--------------
    pgsql/doc:
        TODO (r1.2224 -> r1.2225)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/TODO?r1=1.2224&r2=1.2225)
    pgsql/doc/src/FAQ:
        TODO.html (r1.733 -> r1.734)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/doc/src/FAQ/TODO.html?r1=1.733&r2=1.734)

pgsql-committers by date:

Previous
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: Update wording: < o Allow COMMENT ON dbname to work when
Next
From: momjian@postgresql.org (Bruce Momjian)
Date:
Subject: pgsql: More release notes wording cleanups.