aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorAndres Freund <andres@anarazel.de>2018-01-03 12:00:11 -0800
committerAndres Freund <andres@anarazel.de>2018-01-03 12:39:59 -0800
commitea4cbf8f1050b490d3040e659598bee63494288d (patch)
treea39905c71ce7064988675c1c42cba4d63481d752 /src/backend/access/gist/gist.c
parentd329d2d3e49662eb41b1fec74d55d4738394ba7d (diff)
downloadpostgresql-ea4cbf8f1050b490d3040e659598bee63494288d.tar.gz
postgresql-ea4cbf8f1050b490d3040e659598bee63494288d.zip
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.w7jkljth3e26sduc@alap3.anarazel.de https://postgr.es/m/31122.1514951044@sss.pgh.pa.us Backpatch: 9.5-, where pg_rewind was introduced
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions