From: | Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> |
---|---|
To: | Josh Kupershmidt <schmiddy(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: patch: Allow \dd to show constraint comments |
Date: | 2011-06-19 07:25:40 |
Message-ID: | BANLkTi=YBCZ3OzqOCoJ-nP6cnNTiVz7Gqg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I think the v5 patch should be marked as 'Ready for Committer'
2011/6/18 Josh Kupershmidt <schmiddy(at)gmail(dot)com>:
> On Sat, Jun 18, 2011 at 10:53 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
>> In addition, this pg_comments system view supports 'access method' class, but
>> we cannot set a comment on access methods using COMMENT ON statement.
>
> Well, there are comments for the built-in access methods, i.e.
>
Oops, I missed the comments on initdb stage.
>> Regarding to the data-type of objnamespace, how about an idea to define a new
>> data type such as 'regschema' and cast objnamespace into this type?
>> If we have such data type, user can reference string expression of schema name,
>> and also available to use OID joins.
>
> Are you suggesting we leave the structure of pg_comments unchanged,
> but introduce a new 'regschema' type so that if users want to easily
> display the schema name of an object, they can just do:
>
> SELECT objnamespace::regschema, ...
> FROM pg_comments WHERE ... ;
>
> That seems reasonable to me.
>
Yes, however, it should be discussed in another thread as Robert said.
Thanks,
--
KaiGai Kohei <kaigai(at)kaigai(dot)gr(dot)jp>
From | Date | Subject | |
---|---|---|---|
Next Message | Kohei KaiGai | 2011-06-19 08:48:03 | Re: [v9.2] DROP Reworks Part.0 - 'missing_ok' support of get_object_address |
Previous Message | Robert Haas | 2011-06-19 04:25:24 | Re: SSI tuning points |