Re: Issue in pg_catalog.pg_indexes view definition - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Issue in pg_catalog.pg_indexes view definition
Date
Msg-id CAB7nPqQRqdNG9FtsU0tC5OTEtK+mzGbW7a6wEh1LZjHyAS2V0g@mail.gmail.com
Whole thread Raw
In response to Re: Issue in pg_catalog.pg_indexes view definition  (Dilip Kumar <dilipbalaut@gmail.com>)
Responses Re: Issue in pg_catalog.pg_indexes view definition  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers
On Thu, Jul 14, 2016 at 4:59 PM, Dilip Kumar <dilipbalaut@gmail.com> wrote:
> I was wrong, Actually If we change the view and call function on
> x.indexrelid, It will fix the issue, because pg_get_indexdef(x.indexrelid)
> is non equal clause and of course will not fall in same equivalence class.

-        pg_get_indexdef(I.oid) AS indexdef
+        pg_get_indexdef(X.indexrelid) AS indexdef
Fixing it this way looks like a good idea to me to bypass those cache
lookup errors caused by non-index relations. Now I think that you need
as well to update the regression test output.
-- 
Michael



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Issue in pg_catalog.pg_indexes view definition
Next
From: Amit Langote
Date:
Subject: Re: Issue in pg_catalog.pg_indexes view definition