Postgres Pro
Downloads
Home   >   mailing lists

Thread: BUG #1144: comments don't get propagated

BUG #1144: comments don't get propagated

From
"PostgreSQL Bugs List"
Date:
The following bug has been logged online:

Bug reference:      1144
Logged by:          comments on database

Email address:      Oliver303@aon.at

PostgreSQL version: 7.4

Operating system:   Freebsd 4.9-RELEASE

Description:        comments don't get propagated

Details:

My system:
`uname -r`:  4.9-RELEASE-p3
postgres version
==> select version():   PostgreSQL 7.4.2 on i386-portbld-freebsd4.9,
compiled by GCC 2.95.4

actually it's not a bug, but it's not a feature, definitely. ;-)

I did a "create database testdb" from psql without a file ${HOME}/.pgsqlrc.
The initial database was "template1". Then i tried a "comment on database
testdb is '...';"
==> cannot create comment

--> I'm using LC_ALL=de_AT.ISO8859-15

translated: database comments can be applied to current database only
so I did a "\c testdb"
and then "comment on database testdb is '...';"

success!

but after "\c tempalte1"
"\l+" doesn't give the comment on testdb.

probably the fact is that pg_database is the same across a cluster, but
pg_catalog.pg_description is not.

After I did a "\c testdb" i saw the the comment.

The docu says that pg_catalog.pg_database is shared between the cluster.
Probably the same should be true for pg_description, since all oid are
unique across the cluster. ?!

In my opinion this fact could confuse some people.

BTW:
Could You give an example of an insert statement to pg_description to
circumvent this inconvenience.

thnx Oliver

Re: BUG #1144: comments don't get propagated

From
Bruce Momjian
Date:
PostgreSQL Bugs List wrote:
> I did a "create database testdb" from psql without a file ${HOME}/.pgsqlrc.
> The initial database was "template1". Then i tried a "comment on database
> testdb is '...';"
> ==> cannot create comment
>
> --> I'm using LC_ALL=de_AT.ISO8859-15
>
> translated: database comments can be applied to current database only
> so I did a "\c testdb"
> and then "comment on database testdb is '...';"
>
> success!
>
> but after "\c tempalte1"
> "\l+" doesn't give the comment on testdb.
>
> probably the fact is that pg_database is the same across a cluster, but
> pg_catalog.pg_description is not.
>
> After I did a "\c testdb" i saw the the comment.
>
> The docu says that pg_catalog.pg_database is shared between the cluster.
> Probably the same should be true for pg_description, since all oid are
> unique across the cluster. ?!
>
> In my opinion this fact could confuse some people.
>
> BTW:
> Could You give an example of an insert statement to pg_description to
> circumvent this inconvenience.

Interesting idea having pg_description span databases because oids are
unique.  Yea, that would help the database description problem, but then
oids can wrap around and they wouldn't be unique anymore.

Basically, it would fix this problem, but it might cause more serious
problems other places.

--
  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