Adjust initdb to also not consider fsync'ing failures fatal.
Make initdb's version of this logic look as much like the backend's
as possible. This is much less critical than in the backend since not
so many people use "initdb -S", but we want the same corner-case error
handling in both cases.
Back-patch to 9.3 where initdb -S option was introduced. Before that,
initdb only had to deal with freshly-created data directories, wherein
no failures should be expected.
Abhijit Menon-Sen
Branch
------
REL9_4_STABLE
Details
-------
http://git.postgresql.org/pg/commitdiff/dbde225b144890fb5a40e21f8f624de18ead2f95
Modified Files
--------------
src/bin/initdb/initdb.c | 306 ++++++++++++++++++++++++-----------------------
1 file changed, 155 insertions(+), 151 deletions(-)