Content-Length: 235601 | pFad | http://github.com/postgrespro/postgres/commit/c07d8c963e39980f192e8daca73b7585ef76cc9b

0F Adjust initdb to also not consider fsync'ing failures fatal. · postgrespro/postgres@c07d8c9 · GitHub

Commit c07d8c9

committed

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

1 parent da33a38 commit c07d8c9Copy full SHA for c07d8c9

1 file changed

+155

-151

lines changed

src/bin/initdb
- initdb.c

1 file changed

+155

-151

lines changed

Comments

(0)

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Commit c07d8c9

1 file changed

1 file changed

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier! Saves Data!

File tree

1 file changed

1 file changed

0 commit comments

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier! Saves Data!