| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql-server: Tablespaces. |
| Date: | 2004-06-19 03:40:02 |
| Message-ID: | 40D3B592.50803@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
> Well, it has the same issues as COMMENT ON DATABASE, which we support,
> though crudely.
>
> Perhaps we should think about creating a shared version of
> pg_description so we could have more reasonable support for comments
> on shared objects. I'm not in a hurry for this but it would be a
> reasonable TODO item.
Just add a comment text column to the databases, users, groups and
tablespaces tables. Then special case them in obj_description.
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-06-19 04:22:26 | pgsql-server: Enable thread safety for win32.mak build of PostgreSQL. |
| Previous Message | Bruce Momjian | 2004-06-19 03:09:36 | Re: pgsql-server: Give inet/cidr datatypes their own hash |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Christopher Kings-Lynne | 2004-06-19 03:48:15 | Re: Tablespace patch review |
| Previous Message | Bruce Momjian | 2004-06-19 03:18:44 | Twelve days to feature freeze |