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:41:27
Message-ID: CAB7nPqS6g0BNxAYFHHAKnvGu6gBkCWFC0hxjrW6=nZOnW+kDEw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 14, 2016 at 5:29 PM, Dilip Kumar <dilipbalaut(at)gmail(dot)com> wrote:
>
> On Thu, Jul 14, 2016 at 1:40 PM, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
> wrote:
>>
>> - 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.
>
>
> I observed one regression failure caused by this fix. So fixed the same in
> new patch.

Yes that was rules.out that needed a refresh. Thanks!
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Artur Zakirov 2016-07-14 09:05:58 Re: Bug in to_timestamp().
Previous Message AMatveev 2016-07-14 08:41:07 Re: One process per session lack of sharing