From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Use get_call_result_type() more widely |
Date: | 2022-12-21 07:19:37 |
Message-ID: | CALj2ACVVHf9cGeMrpDnmCfLC3w0sAPv5PqyFSR3dONVpmHhp-g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Dec 21, 2022 at 6:44 AM Michael Paquier <michael(at)paquier(dot)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 | Content-Type | Size |
---|---|---|
v1-0001-Add-another-way-to-build-TupleDesc-in-documentati.patch | application/x-patch | 2.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2022-12-21 07:21:55 | Re: Force streaming every change in logical decoding |
Previous Message | shveta malik | 2022-12-21 07:19:08 | Re: Force streaming every change in logical decoding |