Re: psql's \d functions broken for views in current sources - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: psql's \d functions broken for views in current sources
Date
Msg-id 200010170341.XAA05776@candle.pha.pa.us
Whole thread Raw
In response to Re: psql's \d functions broken for views in current sources  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Was this addressed?


> Hiroshi Inoue <Inoue@tpf.co.jp> 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 be changed first.
> 
> No, pg_views still works --- although it could be made far more
> efficient (don't need the WHERE EXISTS(...) test anymore, just look
> at relkind).  So I don't think that explains why psql is misbehaving.
> 
> You are right that we ought to change the definition of pg_views,
> anyway.
> 
>             regards, tom lane
> 


--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: length coerce for bpchar is broken since 7.0
Next
From: Tom Lane
Date:
Subject: Re: The lightbulb just went on...