Rename pg_rewind's copy_file_range() to avoid conflict with new linux syscall.
authorAndres Freund
Wed, 3 Jan 2018 20:00:11 +0000 (12:00 -0800)
committerAndres Freund
Wed, 3 Jan 2018 20:39:59 +0000 (12:39 -0800)
commitea4cbf8f1050b490d3040e659598bee63494288d
treea39905c71ce7064988675c1c42cba4d63481d752
parentd329d2d3e49662eb41b1fec74d55d4738394ba7d
Rename pg_rewind's copy_file_range() to avoid conflict with new linux syscall.

Upcoming versions of glibc will contain copy_file_range(2), a wrapper
around a new linux syscall for in-kernel copying of data ranges. This
conflicts with pg_rewinds function of the same name.

Therefore rename pg_rewinds version. As our version isn't a generic
copying facility we decided to choose a rewind specific function name.

Per buildfarm animal caiman and subsequent discussion with Tom Lane.

Author: Andres Freund
Discussion:
    https://postgr.es/m/20180103033425[email protected]
    https://postgr.es/m/31122.1514951044@sss.pgh.pa.us
Backpatch: 9.5-, where pg_rewind was introduced
src/bin/pg_rewind/copy_fetch.c