Re: [HACKERS] Cache lookup errors with functions manipulation object addresses - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] Cache lookup errors with functions manipulation object addresses
Date
Msg-id CAB7nPqQWJj6Q0HPwCKiaRvDUBQwhcLn9wCe8RzyKjCR_4aC2_Q@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Cache lookup errors with functions manipulation object addresses  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [HACKERS] Cache lookup errors with functions manipulation object addresses  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
On Thu, Aug 10, 2017 at 9:48 AM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> On Wed, Aug 9, 2017 at 2:47 PM, Aleksander Alekseev
> <a.alekseev@postgrespro.ru> wrote:
>> I believe this patch is "Ready for Committer".
>>
>> The new status of this patch is: Ready for Committer
>
> Thanks for the lookup, but I think that this is still hasty as no
> discussion has happened about a couple of APIs to get object names.
> Types, operators and functions have no "cache lookup" and prefer
> producing names like "???" or "-". We may want to change that. Or not.
> The current patch keeps existing interfaces as much as possible but
> those existing caveats remain.

Attached is a rebased patch set. Álvaro, as you have introduced most
of the problems with 4464303 & friends dated of 2015 when you
introduced get_object_address(), could you look at this patch set?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Rajkumar Raghuwanshi
Date:
Subject: Re: [HACKERS] Parallel Append implementation
Next
From: Etsuro Fujita
Date:
Subject: Re: [HACKERS] Add support for tuple routing to foreign partitions