Comment on Database and Admin Metadata

From: "Kuhn, Dylan K (4520500D)" <Dylan(dot)Kuhn(at)navy(dot)mil>
To: <pgsql-admin(at)postgresql(dot)org>
Cc: <tom(at)demayfamily(dot)net>
Subject: Comment on Database and Admin Metadata
Date: 2003-05-14 16:22:26
Message-ID: 78ED1F30F0D85B4698FBD6CF2A5AC8F5A576D2@NAWECHLKEX01VA.nadsuswe.nads.navy.mil
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Greetings,

We are storing some metadata about a database in the database comment. In short my question is, is there a better place?

We use a version-controlled model for our database design, and would like to know what model version any particular database implements. A client can thereby determine by the model version if it is able to use the database.

Bug #880 (http://archives.postgresql.org/pgsql-bugs/2003-01/msg00131.php) discusses some of the problems with comments on databases. You have to know the current database name to create the comment, but you can't use current_database(), and you can't create a comment on any other database. Also, you have to connect to the database to read the comment (which is not horrible, but not obvious either when looking at commands like '\l+').

This seems like it would be a common problem. I'd like to know if there is a better place for such database-level metadata, and if there are plans to fix/change COMMENT ON DATABASE. Or even if anyone else is deleting and adding records to pg_description like we are to accomplish this.

Thanks,
Dylan Kuhn

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message David F. Skoll 2003-05-14 16:30:43 Re: Comment on Database and Admin Metadata
Previous Message Tom Lane 2003-05-14 16:07:32 Re: Problems configuring --with-python on RedHat7.2