Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready)
От | Michael Paquier |
---|---|
Тема | Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready) |
Дата | |
Msg-id | CAB7nPqQVauEEpSX70M5NKLbAEXYqiCGCBzUCJR5=F-m-SO_sQw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: initdb issue on 64-bit Windows - (Was: [pgsql-packagers] PG 9.6beta2 tarballs are ready) ("Tsunakawa, Takayuki" <tsunakawa.takay@jp.fujitsu.com>) |
Ответы |
Re: initdb issue on 64-bit Windows - (Was:
[pgsql-packagers] PG 9.6beta2 tarballs are ready)
|
Список | pgsql-hackers |
On Fri, Jun 24, 2016 at 11:51 AM, Tsunakawa, Takayuki <tsunakawa.takay@jp.fujitsu.com> wrote: >> From: pgsql-hackers-owner@postgresql.org >> [mailto:pgsql-hackers-owner@postgresql.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@2ndquadrant.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. -- Michael
В списке pgsql-hackers по дате отправления: