Good analysis. Database comments are particularly tricky because
pg_description exists in every database, but is unique. To fix this, we
would need a global pg_description table that would be used _just_ for
database comments.
> Patricia Holben (pholben@greatbridge.com) reports a bug with a
> severity of 3 The lower the number the more severe it is.
>
> Short Description Comments on Database Broken
>
> Long Description When comments are added to a database (testdb
> in this example) (either at the point of creation or using the
> "comment on database ..." command) they may be stored either at
> the system level or within the individual database storage area.
> Depending on how the user is connected, the "\l+" command may
> show the system comment on testdb (connected to template1 for
> example) OR the self-applied comment on testdb (connected to
> testdb) OR the local comment on testdb (connected to a different
> db which has made comments on what the other dbs are). When a
> pg_dumpall command is executed, the dbs are dropped, and then
> the dump file is reloaded, only the self-applied comments exist
> anymore. Mainly this is just confusing. Maybe they should only
> exist in the system area but be accessible to all.
>
> Sample Code
>
>
> No file was uploaded with this report
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an
> appropriate subscribe-nomail command to majordomo@postgresql.org
> so that your message can get through to the mailing list cleanly
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
