Re: Use get_call_result_type() more widely

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Use get_call_result_type() more widely
Date: 2022-12-20 07:32:36
Message-ID: Y6FlFGK/1C0RUCMa@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 19, 2022 at 05:50:03PM -0500, Robert Haas wrote:
> All right, well, I just work here. :-)

Just to give some numbers. The original version of the patch doing
the full switch removed 500 lines of code. The second version that
switches the "non-critical" paths removes 200~ lines.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-12-20 07:38:59 Re: Use get_call_result_type() more widely
Previous Message Michael Paquier 2022-12-20 07:25:43 Re: Refactor SCRAM code to dynamically handle hash type and key length