Re: postgres_fdw - should we tighten up batch_size, fetch_size options against non-numeric values? - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: postgres_fdw - should we tighten up batch_size, fetch_size options against non-numeric values?
Date
Msg-id a10e4ad3-48e4-6b08-8f2b-2dc7eb5f3c4a@oss.nttdata.com
Whole thread Raw
In response to Re: postgres_fdw - should we tighten up batch_size, fetch_size options against non-numeric values?  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers

On 2021/07/01 21:41, Bharath Rupireddy wrote:
> On Thu, Jul 1, 2021 at 6:07 PM Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
>>
>> On 2021/07/01 13:16, Bharath Rupireddy wrote:
>>> On Thu, Jul 1, 2021 at 8:23 AM Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
>>>> The recent commit 61d599ede7 documented that the type of those options is
>>>> floating point. But the docs still use "is a numeric value" in the descriptions
>>>> of them. Probably it should be replaced with "is a floating point value" there.
>>>> If we do this, isn't it better to use "floating point" even in the error message?
>>>
>>> Agreed. PSA v5 patch.
>>
>> Thanks for updating the patch! LGTM.
>> Barring any objection, I will commit this patch.
> 
> Thanks.
> 
>> One question is; should we back-patch this? This is not a bug fix,
>> so I'm not sure if it's worth back-patching that to already-released versions.
>> But it may be better to do that to v14.
> 
> IMO, it's a good-to-have fix in v14. But, -1 for backpatching to v13
> and lower branches.

Agreed. So I pushed the patch to master and v14. Thanks!

Regards,

-- 
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Refactor "mutually exclusive options" error reporting code in parse_subscription_options
Next
From: Gurjeet Singh
Date:
Subject: Warn if initdb's --sync-only option is mixed with other options