aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/jsonfuncs.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2015-05-29 17:02:58 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2015-05-29 17:02:58 -0400
commit1943c000b7a22d3ca334196cfe3f7b8159b210c2 (patch)
tree94f1c0ee02196cc1b03e8f8e721937491d8e9816 /src/backend/utils/adt/jsonfuncs.c
parent57e1138bcc621ffeb8b1f1379ac4016a5c34d43e (diff)
downloadpostgresql-1943c000b7a22d3ca334196cfe3f7b8159b210c2.tar.gz
postgresql-1943c000b7a22d3ca334196cfe3f7b8159b210c2.zip
initdb -S should now have an explicit check that $PGDATA is valid.
The fsync code from the backend essentially assumes that somebody's already validated PGDATA, at least to the extent of it being a readable directory. That's safe enough for initdb's normal code path too, but "initdb -S" doesn't have any other processing at all that touches the target directory. To have reasonable error-case behavior, add a pg_check_dir call. Per gripe from Peter E.
Diffstat (limited to 'src/backend/utils/adt/jsonfuncs.c')
0 files changed, 0 insertions, 0 deletions