aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistvacuum.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
commite3fdb7c00e783ed4b490554ab6bbaccad341c244 (patch)
tree96aa96d20ba5acc2931492fffebb1cfc53179835 /src/backend/access/gist/gistvacuum.c
parent0fb69340b2352d8491d15c11156d16988676f71f (diff)
downloadpostgresql-e3fdb7c00e783ed4b490554ab6bbaccad341c244.tar.gz
postgresql-e3fdb7c00e783ed4b490554ab6bbaccad341c244.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/gistvacuum.c')
0 files changed, 0 insertions, 0 deletions