aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeModifyTable.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2022-03-17 11:25:02 +0900
committerMichael Paquier <michael@paquier.xyz>2022-03-17 11:25:02 +0900
commitf6f0db4d62400ff88f523dcc4d7e25f9506bc0d8 (patch)
tree7182bcb12d2ac80de33547c9f1693800f1231dd6 /src/backend/executor/nodeModifyTable.c
parentc91f71b9dc91ef95e1d50d6d782f477258374fc6 (diff)
downloadpostgresql-f6f0db4d62400ff88f523dcc4d7e25f9506bc0d8.tar.gz
postgresql-f6f0db4d62400ff88f523dcc4d7e25f9506bc0d8.zip
Fix pg_tablespace_location() with in-place tablespaces
Using this system function with an in-place tablespace (created when allow_in_place_tablespaces is enabled by specifying an empty string as location) caused a failure when using readlink(), as the tablespace is, in this case, not a symbolic link in pg_tblspc/ but a directory. Rather than getting a failure, the commit changes pg_tablespace_location() so as a relative path to the data directory is returned for in-place tablespaces, to make a difference between tablespaces created when allow_in_place_tablespaces is enabled or not. Getting a path rather than an empty string that would match the CREATE TABLESPACE command in this case is more useful for tests that would like to rely on this function. While on it, a regression test is added for this case. This is simple to add in the main regression test suite thanks to regexp_replace() to mask the part of the tablespace location dependent on its OID. Author: Michael Paquier Reviewed-by: Kyotaro Horiguchi, Thomas Munro Discussion: https://postgr.es/m/YiG1RleON1WBcLnX@paquier.xyz
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions