Re: [HACKERS] pg_comments (was: Allow \dd to show constraint comments)

2011-11-09 Thread Robert Haas
On Wed, Nov 9, 2011 at 3:38 AM, Thom Brown wrote: > On 9 November 2011 02:42, Robert Haas wrote: >> On Tue, Nov 8, 2011 at 8:12 PM, Thom Brown wrote: >>> Why is this marked as done on with Wiki's todo list? >> >> I assume you're referring to this item: >> >> -- >> \dd is missing comments for sev

Re: [HACKERS] pg_comments (was: Allow \dd to show constraint comments)

2011-11-09 Thread Thom Brown
On 9 November 2011 02:42, Robert Haas wrote: > On Tue, Nov 8, 2011 at 8:12 PM, Thom Brown wrote: >> Why is this marked as done on with Wiki's todo list? > > I assume you're referring to this item: > > -- > \dd is missing comments for several types of objects.  Comments are > not handled at all fo

Re: [HACKERS] pg_comments (was: Allow \dd to show constraint comments)

2011-11-08 Thread Robert Haas
On Tue, Nov 8, 2011 at 8:12 PM, Thom Brown wrote: > Why is this marked as done on with Wiki's todo list? I assume you're referring to this item: -- \dd is missing comments for several types of objects. Comments are not handled at all for some object types, and are handled by both \dd and the in

Re: [HACKERS] pg_comments (was: Allow \dd to show constraint comments)

2011-11-08 Thread Thom Brown
On 17 October 2011 03:04, Robert Haas wrote: > On Fri, Oct 14, 2011 at 11:12 AM, Robert Haas wrote: >> On Wed, Oct 12, 2011 at 10:20 PM, Josh Kupershmidt >> wrote: On the third hand, Josh's previous batch of changes to clean up psql's behavior in this area are clearly a huge improveme

Re: [HACKERS] pg_comments (was: Allow \dd to show constraint comments)

2011-10-21 Thread Marti Raudsepp
On Mon, Oct 17, 2011 at 05:04, Robert Haas wrote: > Hearing no cries of "oh, yes, please", I'm marking this Returned with > Feedback for now.  We can always revisit it if we hear that more > people want it. I think this would be an improvement, but it's pretty low on my wishlist. I haven't checke

Re: [HACKERS] pg_comments (was: Allow \dd to show constraint comments)

2011-10-16 Thread Robert Haas
On Fri, Oct 14, 2011 at 11:12 AM, Robert Haas wrote: > On Wed, Oct 12, 2011 at 10:20 PM, Josh Kupershmidt wrote: >>> On the third hand, Josh's previous batch of changes to clean up >>> psql's behavior in this area are clearly a huge improvement: you can >>> now display the comment for nearly anyt

Re: [HACKERS] pg_comments (was: Allow \dd to show constraint comments)

2011-10-14 Thread Robert Haas
On Wed, Oct 12, 2011 at 10:20 PM, Josh Kupershmidt wrote: >> On the third hand, Josh's previous batch of changes to clean up >> psql's behavior in this area are clearly a huge improvement: you can >> now display the comment for nearly anything by running the appropriate >> \d command for whatever

Re: [HACKERS] pg_comments (was: Allow \dd to show constraint comments)

2011-10-12 Thread Josh Kupershmidt
On Wed, Oct 12, 2011 at 2:49 PM, Robert Haas wrote: > So, I think the critical question for this patch is "do we want > this?". Yep. Or put another way, are the gains worth having another system view we'll have to maintain forever? > Tom didn't like it, In [1], Tom seemed to be mainly angling f

Re: [HACKERS] pg_comments (was: Allow \dd to show constraint comments)

2011-10-12 Thread Robert Haas
On Sun, Sep 11, 2011 at 10:11 AM, Josh Kupershmidt wrote: > On Sat, Sep 10, 2011 at 7:47 PM, Thom Brown wrote: >> Just tested this out on current master.  I tried this on every object >> capable of having a comment, and the view reports all of them with the >> correct details.  Doc changes look f

Re: [HACKERS] pg_comments

2010-09-24 Thread Tom Lane
KaiGai Kohei writes: > It seems to me the query should be fixed up as follows: > : > WHERE > d.classoid = (SELECT oid FROM pg_class WHERE relname = 'pg_largeobject' > AND relnamespace = (SELECT oid FROM pg_namespace > WHERE n

Re: [HACKERS] pg_comments

2010-09-24 Thread Robert Haas
2010/9/24 KaiGai Kohei : > If and when user create a table named 'pg_largeobject' on anywhere except > for the 'pg_catalog' schema, the (SELECT oid FROM pg_class WHERE relname = > 'pg_largeobject') may not return 2613. Oh, dear, how embarassing. Perhaps it should be written as: d.classoid = 'pg_

Re: [HACKERS] pg_comments

2010-09-23 Thread KaiGai Kohei
Robert, I noticed a problem at the definition of the view. : +UNION ALL +SELECT + d.objoid, d.classoid, d.objsubid, + 'large object'::text AS objtype, + NULL::oid AS objnamespace, + d.objoid::text AS objname, + d.description +FROM + pg_description d +

Re: [HACKERS] pg_comments

2010-09-20 Thread Robert Haas
On Mon, Sep 20, 2010 at 1:07 AM, Tom Lane wrote: > Robert Haas writes: >> In view of the foregoing problems, I'd like to propose adding a new >> system view, tentatively called pg_comments, which lists all of the >> comments for everything in the system in such a way that it's >> reasonably possi

Re: [HACKERS] pg_comments

2010-09-19 Thread Tom Lane
Robert Haas writes: > In view of the foregoing problems, I'd like to propose adding a new > system view, tentatively called pg_comments, which lists all of the > comments for everything in the system in such a way that it's > reasonably possible to do further filtering out the output in ways > tha