| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Nikhil Sontakke <nikhils(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: initdb fails to initialize data directory |
| Date: | 2018-04-19 13:38:43 |
| Message-ID: | 20180419133843.3iyxzjtgvx65b37u@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2018-04-19 13:41:43 | Re: Problem while setting the fpw with SIGHUP |
| Previous Message | Konstantin Knizhnik | 2018-04-19 13:24:11 | Re: Built-in connection pooling |