Postgres Pro
Downloads
Home   >   mailing lists

Re: Use get_call_result_type() more widely - Mailing list pgsql-hackers

From Bharath Rupireddy
Subject Re: Use get_call_result_type() more widely
Date
Msg-id CALj2ACVVHf9cGeMrpDnmCfLC3w0sAPv5PqyFSR3dONVpmHhp-g@mail.gmail.com
Whole thread Raw
In response to Re: Use get_call_result_type() more widely  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
Tree view 
On Wed, Dec 21, 2022 at 6:44 AM Michael Paquier <michael@paquier.xyz> wrote:
>
> I have applied v2-0001.

Thanks for taking care of this.

By seeing the impact that get_call_result_type() can have for the
functions that are possibly called repeatedly, I couldn't resist
sharing a patch (attached herewith) that adds a note of caution and
another way to build TupleDesc in the documentation to help developers
out there. Thoughts?

--
Bharath Rupireddy
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com
Attachment

pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: Force streaming every change in logical decoding
Next
From: Masahiko Sawada
Date:
Subject: Re: Force streaming every change in logical decoding