postgresql/src/bin
Tom Lane 99f50dd720 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.
2015-05-29 17:02:58 -04:00
..
initdb initdb -S should now have an explicit check that $PGDATA is valid. 2015-05-29 17:02:58 -04:00
pg_basebackup Translation updates 2015-05-18 08:38:34 -04:00
pg_config Translation updates 2015-05-18 08:38:34 -04:00
pg_controldata Translation updates 2015-05-18 08:38:34 -04:00
pg_ctl Translation updates 2015-05-18 08:38:34 -04:00
pg_dump Translation updates 2015-05-18 08:38:34 -04:00
pg_resetxlog Translation updates 2015-05-18 08:38:34 -04:00
pgevent Remove inappropriate EXPORTS line. 2014-02-19 21:08:50 -05:00
psql Translation updates 2015-05-18 08:38:34 -04:00
scripts Translation updates 2015-05-18 08:38:34 -04:00
Makefile Update copyright for 2014 2014-01-07 16:05:30 -05:00