> From: Tom Lane [mailto:tgl@sss.pgh.pa.us]
> "Etsuro Fujita" <fujita.etsuro@lab.ntt.co.jp> writes:
> > As described in the reference manual for COPY, we should to check file's
path
> > format not to allow relative path. Please find attached a patch.
>
> The argument for disallowing writing to a relative path is to make it
> harder to accidentally overwrite a database file. That argument does
> not apply to COPY IN, so I'm not convinced we should impose an
> additional restriction. It's not out of the question that this would
> break real-world use-cases --- imagine someone whose workflow involves
> copying data files across a network to a directory accessible to the
> server (and quite possibly specified by a relative path) and then doing
> COPY IN.
>
> In any case, this patch is missing documentation updates, specifically
> the paragraph in the COPY reference page that it falsifies.
Agreed. I'd like to withdraw the patch sent in the earlier post, and propose to
update the documentation in the COPY reference page. Please find attached a
patch.
Thanks,
Best regards,
Etsuro Fujita