Re: Use get_call_result_type() more widely
От
Bharath Rupireddy
Тема
Re: Use get_call_result_type() more widely
Дата
Msg-id
CALj2ACVVHf9cGeMrpDnmCfLC3w0sAPv5PqyFSR3dONVpmHhp-g@mail.gmail.com
Ответ на
Re: Use get_call_result_type() more widely (Michael Paquier)
Список
Дерево обсуждения
Use get_call_result_type() more widely Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Use get_call_result_type() more widely Tom Lane <tgl@sss.pgh.pa.us>
Re: Use get_call_result_type() more widely Robert Haas <robertmhaas@gmail.com>
Re: Use get_call_result_type() more widely Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: Use get_call_result_type() more widely Robert Haas <robertmhaas@gmail.com>
Re: Use get_call_result_type() more widely Tom Lane <tgl@sss.pgh.pa.us>
Re: Use get_call_result_type() more widely Robert Haas <robertmhaas@gmail.com>
Re: Use get_call_result_type() more widely Michael Paquier <michael@paquier.xyz>
Re: Use get_call_result_type() more widely Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Use get_call_result_type() more widely Michael Paquier <michael@paquier.xyz>
Re: Use get_call_result_type() more widely Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Use get_call_result_type() more widely Michael Paquier <michael@paquier.xyz>
Re: Use get_call_result_type() more widely Tom Lane <tgl@sss.pgh.pa.us>
Re: Use get_call_result_type() more widely Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Use get_call_result_type() more widely Tom Lane <tgl@sss.pgh.pa.us>
Re: Use get_call_result_type() more widely Michael Paquier <michael@paquier.xyz>
Re: Use get_call_result_type() more widely Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Re: Use get_call_result_type() more widely Michael Paquier <michael@paquier.xyz>
On Wed, Dec 21, 2022 at 6:44 AM Michael Paquier 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
В списке pgsql-hackers по дате отправления
