Comments on Database Broken
От | pgsql-bugs@postgresql.org |
---|---|
Тема | Comments on Database Broken |
Дата | |
Msg-id | 200105211823.f4LINU283557@hub.org обсуждение исходный текст |
Ответы |
Re: Comments on Database Broken
Re: Comments on Database Broken |
Список | pgsql-bugs |
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 ondatabase ..." command) they may be stored either at the system level or within the individual database storage area. Dependingon how the user is connected, the "\l+" command may show the system comment on testdb (connected to template1 forexample) OR the self-applied comment on testdb (connected to testdb) OR the local comment on testdb (connected to a differentdb 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
В списке pgsql-bugs по дате отправления: