Introduce file_copy_method setting.
authorThomas Munro <tmunro@postgresql.org>
Tue, 8 Apr 2025 08:52:47 +0000 (20:52 +1200)
committerThomas Munro <tmunro@postgresql.org>
Tue, 8 Apr 2025 09:35:38 +0000 (21:35 +1200)
commitf78ca6f3ebbbff8c675c34b8ee61047223073866
treec3543200c7b119226fb6b1266db6dfd463b02267
parent042a66291b04f473cbc72f95f07438abd75ae3a9
Introduce file_copy_method setting.

It can be set to either COPY (the default) or CLONE if the system
supports it.  CLONE causes callers of copydir(), currently CREATE
DATABASE ... STRATEGY=FILE_COPY and ALTER DATABASE ... SET TABLESPACE =
..., to use copy_file_range (Linux, FreeBSD) or copyfile (macOS) to copy
files instead of a read-write loop over the contents.

CLONE gives the kernel the opportunity to share block ranges on
copy-on-write file systems and push copying down to storage on others,
depending on configuration.  On some systems CLONE can be used to clone
large databases quickly with CREATE DATABASE ... TEMPLATE=source
STRATEGY=FILE_COPY.

Other operating systems could be supported; patches welcome.

Co-authored-by: Nazir Bilal Yavuz <byavuz81@gmail.com>
Reviewed-by: Robert Haas <robertmhaas@gmail.com>
Reviewed-by: Ranier Vilela <ranier.vf@gmail.com>
Discussion: https://postgr.es/m/CA%2BhUKGLM%2Bt%2BSwBU-cHeMUXJCOgBxSHLGZutV5zCwY4qrCcE02w%40mail.gmail.com
doc/src/sgml/config.sgml
doc/src/sgml/ref/alter_database.sgml
doc/src/sgml/ref/create_database.sgml
src/backend/storage/file/copydir.c
src/backend/utils/activity/wait_event_names.txt
src/backend/utils/misc/guc_tables.c
src/backend/utils/misc/postgresql.conf.sample
src/include/storage/copydir.h
src/tools/pgindent/typedefs.list