From: | pgsql-bugs(at)postgresql(dot)org |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Comments on Database Broken |
Date: | 2001-05-21 18:23:30 |
Message-ID: | 200105211823.f4LINU283557@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Patricia Holben (pholben(at)greatbridge(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2001-05-21 19:09:41 | Re: Comments on Database Broken |
Previous Message | pgsql-bugs | 2001-05-21 17:41:07 | psql dumps core when entering invalid backslash command |