Re: can we use different function in place of atoi in vacuumdb.c file

From: Surafel Temesgen <surafel3000(at)gmail(dot)com>
To: Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: can we use different function in place of atoi in vacuumdb.c file
Date: 2020-01-27 07:15:23
Message-ID: CALAY4q_-Vq1H=L3s__OhNFhQ5+xCPzK6D7HgrwWWnwTAPsXsSw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,
On Thu, Jan 23, 2020 at 3:56 PM Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>
wrote:

> Hi all,
> While reviewing one patch, I found that if we give any non-integer string
> to atoi (say aa), then it is returning zero(0) as output so we are not
> giving any error(assuming 0 as valid argument) and continuing our
> operations.
>
> Ex:
> Let say, we gave "-P aa" (patch is in review[1]), then it will disable
> parallel vacuum because atoi is returning zero as parallel degree but
> ideally it should give error or at least it should not disable parallel
> vacuum.
>
> I think, in-place of atoi, we should use different function ( defGetInt32,
> strtoint) or we can write own function.
>
> Thoughts?
>
> [1]:
> https://www.postgresql.org/message-id/CA%2Bfd4k6DgwtQSr4%3DUeY%2BWbGuF7-oD%3Dm-ypHPy%2BsYHiXZc%2BhTUQ%40mail.gmail.com
> --
>

For server side there are also scanint8 function for string parsing and for
Clint side we can use strtoint function that didn't have the above issue
and it accept char pointer which is I think suitable for [1] usage.

regards

Surafel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-01-27 07:55:56 Re: [PATCH] /src/backend/access/transam/xlog.c, tiny improvements
Previous Message Takashi Menjo 2020-01-27 07:01:15 RE: [PoC] Non-volatile WAL buffer