Re: xlog location arithmetic - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: xlog location arithmetic
Date
Msg-id CAHGQGwHsDkjnHzPugEHqnvd213v278feUrD0a+XQHgwq_nMtUw@mail.gmail.com
Whole thread Raw
In response to Re: xlog location arithmetic  (Euler Taveira de Oliveira <euler@timbira.com>)
Responses Re: xlog location arithmetic  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Sun, Feb 26, 2012 at 8:53 AM, Euler Taveira de Oliveira
<euler@timbira.com> wrote:
> On 25-02-2012 09:23, Magnus Hagander wrote:
>> Do we even *need* the validate_xlog_location() function? If we just
>> remove those calls, won't we still catch all the incorrectly formatted
>> ones in the errors of the sscanf() calls? Or am I too deep into
>> weekend-mode and missing something obvious?
>>
> sscanf() is too fragile for input sanity check. Try
> pg_xlog_location_diff('12/3', '-10/0'), for example. I won't object removing
> that function if you protect xlog location input from silly users.

After this patch will have been committed, it would be better to change
pg_xlogfile_name() and pg_xlogfile_name_offset() so that they use
the validate_xlog_location() function to validate the input.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Ants Aasma
Date:
Subject: Re: Initial 9.2 pgbench write results
Next
From: Shigeru Hanada
Date:
Subject: Re: How to know a table has been modified?