Remove initdb's rather gratuitous check to see if the backend created a

flat password file, because it never will anymore.  We had managed to
miss this during the recent flat-file-ectomy because it only happens if
--pwfile or --pwprompt is specified to initdb.  Apparently, few hackers
use those.  Reported by Erik Rijkers.

diff --git a/src/bin/initdb/initdb.c b/src/bin/initdb/initdb.c
index b6998f36fd42bc41253d8053c96c5451f1691c2d..b2e6a23c32ffedfaafc6b227ebf7925ec59306de 100644 (file)
--- a/src/bin/initdb/initdb.c
+++ b/src/bin/initdb/initdb.c
@@ -1434,8 +1434,6 @@ get_set_pwd(void)
 
        char       *pwd1,
                           *pwd2;
-       char            pwdpath[MAXPGPATH];
-       struct stat statbuf;
 
        if (pwprompt)
        {
@@ -1505,16 +1503,6 @@ get_set_pwd(void)
        PG_CMD_CLOSE;
 
        check_ok();
-
-       snprintf(pwdpath, sizeof(pwdpath), "%s/global/pg_auth", pg_data);
-       if (stat(pwdpath, &statbuf) != 0 || !S_ISREG(statbuf.st_mode))
-       {
-               fprintf(stderr,
-                               _("%s: The password file was not generated. "
-                                 "Please report this problem.\n"),
-                               progname);
-               exit_nicely();
-       }
 }
 
 /*