Re: Issue in pg_catalog.pg_indexes view definition

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Issue in pg_catalog.pg_indexes view definition
Date: 2016-07-14 08:10:09
Message-ID: CAB7nPqQRqdNG9FtsU0tC5OTEtK+mzGbW7a6wEh1LZjHyAS2V0g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 14, 2016 at 4:59 PM, Dilip Kumar <dilipbalaut(at)gmail(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2016-07-14 08:15:46 Re: Issue in pg_catalog.pg_indexes view definition
Previous Message Amit Langote 2016-07-14 08:07:40 Re: Issue in pg_catalog.pg_indexes view definition