On Tue, Nov 29, 2016 at 1:33 PM, Michael Paquier <michael.paqu...@gmail.com> wrote: > On Fri, Nov 25, 2016 at 4:41 PM, Michael Paquier > <michael.paqu...@gmail.com> wrote: >> On Fri, Nov 25, 2016 at 4:02 PM, Ideriha, Takeshi >> <ideriha.take...@jp.fujitsu.com> wrote: >>> I applied your fixed patch and new one, and confirmed the applied source >>> passed the tests successfully. And I also checked manually the error >>> messages were emitted successfully when cr/lf are included in dbname or >>> rolename or data_directory. >>> >>> AFAICT, this patch satisfies the concept discussed before. So I’ve switched >>> this patch “Ready for Committer”. >> >> Thanks for the review, Ideriha-san. (See you next week perhaps?) > > Patch moved to CF 2017-01.
And nothing has happened since, the patch rotting a bit because of a conflict in pg_dump's TAP tests. Attached is a rebased version. -- Michael
0001-Forbid-newline-and-carriage-return-characters-in-dat.patch
Description: Binary data
0002-Ensure-clean-up-of-data-directory-even-with-restrict.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
