aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gistbuildbuffers.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2022-01-31 12:05:37 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2022-01-31 12:05:37 -0500
commitc10f830c511f0ba3e6f4c9d99f444d39e30440c8 (patch)
treeb32f2568f2a3d243acbf29113ac1c87a8bae8520 /src/backend/access/gist/gistbuildbuffers.c
parentc89f409749c35bf18fab8e025a34645dd925390c (diff)
downloadpostgresql-c10f830c511f0ba3e6f4c9d99f444d39e30440c8.tar.gz
postgresql-c10f830c511f0ba3e6f4c9d99f444d39e30440c8.zip
Make canonicalize_path() more canonical.
Teach canonicalize_path() how to strip all unnecessary uses of "." and "..", replacing the previous ad-hoc code that got rid of only some such cases. In particular, we can always remove all such uses from absolute paths. The proximate reason to do this is that Windows rejects paths involving ".." in some cases (in particular, you can't put one in a symlink), so we ought to be sure we don't use ".." unnecessarily. Moreover, it seems like good cleanup on general principles. There is other path-munging code that could be simplified now, but we'll leave that for followup work. It is tempting to call this a bug fix and back-patch it. On the other hand, the misbehavior can only be reached if a highly privileged user does something dubious, so it's not unreasonable to say "so don't do that". And this patch could result in unexpected behavioral changes, in case anybody was expecting uses of ".." to stay put. So at least for now, just put it in HEAD. Shenhao Wang, editorialized a bit by me Discussion: https://postgr.es/m/OSBPR01MB4214FA221FFE046F11F2AD74F2D49@OSBPR01MB4214.jpnprd01.prod.outlook.com
Diffstat (limited to 'src/backend/access/gist/gistbuildbuffers.c')
0 files changed, 0 insertions, 0 deletions