Re: [HACKERS] psql's \d functions broken for views in current sources

2000-10-16 Thread Bruce Momjian
Was this addressed? > Hiroshi Inoue <[EMAIL PROTECTED]> writes: > > Tom Lane wrote: > >> I assume this breakage is from the recent RELKIND_VIEW change; > >> probably psql didn't get updated to know about the new relkind. > > > Probably psql uses pg_views though I don't remember correctly. > > I

Re: [HACKERS] psql's \d functions broken for views in current sources

2000-09-24 Thread Tom Lane
Hiroshi Inoue <[EMAIL PROTECTED]> writes: > Tom Lane wrote: >> I assume this breakage is from the recent RELKIND_VIEW change; >> probably psql didn't get updated to know about the new relkind. > Probably psql uses pg_views though I don't remember correctly. > It seemd that pg_views(initdb) should

Re: [HACKERS] psql's \d functions broken for views in current sources

2000-09-24 Thread Hiroshi Inoue
Tom Lane wrote: > psql has some problems with views in current CVS: \d doesn't show views, > and if you do \d on a specific view, it doesn't identify it as a view > and doesn't show the view definition rule. > > I assume this breakage is from the recent RELKIND_VIEW change; > probably psql didn'

[HACKERS] psql's \d functions broken for views in current sources

2000-09-23 Thread Tom Lane
psql has some problems with views in current CVS: \d doesn't show views, and if you do \d on a specific view, it doesn't identify it as a view and doesn't show the view definition rule. I assume this breakage is from the recent RELKIND_VIEW change; probably psql didn't get updated to know about t