Re: initdb fails to initialize data directory
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Nikhil Sontakke <nikhils@2ndquadrant.com>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2018-04-19T13:38:43Z
Lists: pgsql-hackers
Nikhil Sontakke wrote: > Intrigued, on digging down further, this is happening because we are > not using a long enough buffer to accept the output of "postgres -V" > in the find_other_exec() function. In our case, we had used > --with-extra-version option with configure which caused the output of > "postgres -V" to go a little beyond the current "line" variable size. > This caused the strcmp to fail leading to initdb refusing to > initialize any data directories at all. Wow, that seems pretty silly nowadays. Will push in a jiffy. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Enlarge find_other_exec's meager fgets buffer
- e668507d36f8 9.4.18 landed
- e2f3b6560383 10.4 landed
- e160fa005e80 9.5.13 landed
- cea5f9aa1244 11.0 landed
- b3f4742aab82 9.6.9 landed
- 070179a4a2f8 9.3.23 landed