Re: [PATCH] readlink missing nul-termination in pg_rewind - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [PATCH] readlink missing nul-termination in pg_rewind
Date
Msg-id CAB7nPqQiTjooZS=6ypLubae3JNcOc1b-HfxtcSoM5E_kb94zCA@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] readlink missing nul-termination in pg_rewind  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, May 29, 2015 at 1:46 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Abhijit Menon-Sen <ams@2ndQuadrant.com> writes:
>> P.S. Also in passing, I note that pg_rewind will follow links under any
>> directory anywhere named pg_tblspc (which probably doesn't matter), and
>> does not follow pg_xlog if it's a symlink (which probably does). If you
>> want, I can submit a trivial patch for the latter.
>
> As far as that goes, I think it does look at the whole parentpath, which
> means it would not be fooled by sub-subdirectories named pg_tblspc.
> A bigger problem is that whoever coded this forgot that parentpath could
> be null, which I blame on the lack of an API specification for the
> function.

Oh, thanks for pushing a fix for that. It was missed during the review...
-- 
Michael



pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: pg_upgrade resets timeline to 1
Next
From: Gavin Flower
Date:
Subject: Re: pg_upgrade resets timeline to 1