Re: Bug #880: COMMENT ON DATABASE depends on current database - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: Bug #880: COMMENT ON DATABASE depends on current database
Date
Msg-id 200301262302.h0QN28414934@candle.pha.pa.us
Whole thread Raw
In response to Re: Bug #880: COMMENT ON DATABASE depends on current database  (Bhuvan A <bhuvansql@myrealbox.com>)
Responses Re: Bug #880: COMMENT ON DATABASE depends on current database  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-bugs
Bhuvan A wrote:
> > Long Description PostgreSQL has mechanism for commenting databases.
> > Database comments can by read by obj_description(oid), psql \l+ command
> > use it. Database comments should be global, but they are not, when we do
> > \l+ on one database, and then on other, results will be different. I
> > consider it is a bug, database is global object (You can connect to it
> > from any database) but their comments are not.
> >
>
> I too consider it as a bug. But why no response? I hope someone is
> hearing.

You can only create a comment on the current database:

    test=> comment on database template1 is 'xx';
    ERROR:  Database comments may only be applied to the current database

Do we have psql -l to connect to all the databases to collect comments?
I guess we could _try_ to connect to as many databases as possible, but
it seems a little overly complex to me.  What do others think?

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-bugs by date:

Previous
From: Bradley Baetz
Date:
Subject: Re: New hashed IN code ignores distinctiveness of subquery
Next
From: Tom Lane
Date:
Subject: Re: New hashed IN code ignores distinctiveness of subquery