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

From Tom Lane
Subject Re: psql's \d functions broken for views in current sources
Date
Msg-id 15807.969845870@sss.pgh.pa.us
Whole thread Raw
In response to Re: psql's \d functions broken for views in current sources  (Hiroshi Inoue <Inoue@tpf.co.jp>)
Responses Re: psql's \d functions broken for views in current sources
List pgsql-hackers
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


pgsql-hackers by date:

Previous
From: Hiroshi Inoue
Date:
Subject: Re: psql's \d functions broken for views in current sources
Next
From: Zeugswetter Andreas SB
Date:
Subject: Q: How to #ifdef for dlopen() or a specific OS Version