Re: Bug #880: COMMENT ON DATABASE depends on current database

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Bhuvan A <bhuvansql(at)myrealbox(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bug #880: COMMENT ON DATABASE depends on current database
Date: 2003-01-26 23:02:08
Message-ID: 200301262302.h0QN28414934@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2003-01-26 23:51:18 Re: New hashed IN code ignores distinctiveness of subquery
Previous Message Bradley Baetz 2003-01-26 22:37:39 Re: New hashed IN code ignores distinctiveness of subquery