Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)

Michael Paquier wrote:
> On Fri, Jun 24, 2016 at 11:51 AM, Tsunakawa, Takayuki
> <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> wrote:
> >> From: pgsql-hackers-owner(at)postgresql(dot)org
> >> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Michael Paquier
> >> Sent: Friday, June 24, 2016 11:37 AM
> >> On Fri, Jun 24, 2016 at 11:33 AM, Craig Ringer <craig(at)2ndquadrant(dot)com>
> >> wrote:
> >> > It might be worth testing that out and adding an initdb startup
> >> > flag to create the directory, since initdb is such a PITA to
> >> > debug.
> >>
> >> I was more thinking about putting that under -DDEBUG for example.
> >
> > I think just the existing option -d (--debug) and/or -n (--no-clean)
> > would be OK.
>
> If the majority thinks that an option switch is more adapted, I won't
> fight it strongly. Just please let's not mess up with the behavior of
> the existing options.

I think creating crashdumps/ when both -d and -n are specified is a bit
odd but reasonable.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services