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.
Branch ------ REL9_3_STABLE Details ------- http://git.postgresql.org/pg/commitdiff/c2b68b1f7d6de9e749d037a09c5875742e8e6250 Modified Files -------------- src/bin/initdb/initdb.c | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) -- Sent via pgsql-committers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-committers
