Re: Failed to run initdb - not resolved bug 5130 - Mailing list pgsql-bugs
From | Tomas Studva |
---|---|
Subject | Re: Failed to run initdb - not resolved bug 5130 |
Date | |
Msg-id | 27330525.post@talk.nabble.com Whole thread Raw |
In response to | Re: Failed to run initdb - not resolved bug 5130 (Robert Haas <robertmhaas@gmail.com>) |
Responses |
Re: Failed to run initdb - not resolved bug 5130
|
List | pgsql-bugs |
Hi, I have some time now. I've tried to compile postgres from CVS but wihout success. I don't have visual studio 2005 installed so I've tried eclipse + MinGw. I checked out postgres from cvs branch "REL8_4_STABLE". But I wasn't able to compile it. I don't know how to configure builders to launch makefiles or what to do. Any help will be apprecciated and write in-depth receipe, I am not a C/C++ developer (I am Java oriented). Tomas Robert Haas wrote: >=20 > 2010/1/2 Tomas Studva <tstudva@gmail.com>: >> Hi all gurus, >> >> I've encountered on my computer this bug. I will try to describe all what >> I >> have discovered till now. >> >> 1, this bug happened a few times before and wasn't resolved: >> =C2=A0 bug 5130 - >> http://www.mail-archive.com/pgsql-bugs@postgresql.org/msg24810.html >> =C2=A0 bug 5222 - >> http://archives.postgresql.org/pgsql-bugs/2009-12/msg00004.php >> =C2=A0 bug 4691 - >> http://archives.postgresql.org/pgsql-bugs/2009-03/msg00028.php >> =C2=A0 ? - http://forums.enterprisedb.com/posts/list/1845.page >> I think the problem was always the same. >> >> My case is WIN XP SP 2 and also when applied SP3. My system has only one >> speciality as I know, that is I have windows installed on F partition. >> >> Problem description: >> >> I tried install with one click installer, it ends with error >> postgresql.conf >> not found. In log it is failing on initdb, which clears data dir after >> failure. Uninstaller is not working, do nothing when runned. When run >> installation again, then upgrade mode is run, because installation is >> found. >> This can be tricked by deleting installation from registry and deleting >> win >> service, then new install is possible. >> >> I was installing on path F:\Program Files\PostgreSQL\8.4 and also tried >> C:\Program Files\PostgreSQL\8.4, problem is probably not with install >> path. >> >> OK, what more I have tried. MS Visuall C++ redistr. I uninstalled, so the >> one with postgres comming were installed surely. I tried to enable debug >> output, but it gives no new information. I was reading initdb sources and >> problem is probably in this part, because I see message "selecting >> default >> max_connections " then one error message. It looks for me as snprintf is >> not >> executed or reached or etc. >> >> ------------------------------------------------------------------------= ----- >> =C2=A0 printf(_("selecting default max_connections ... ")); >> =C2=A0 fflush(stdout); >> >> =C2=A0 for (i =3D 0; i < connslen; i++) >> =C2=A0 { >> =C2=A0 =C2=A0 =C2=A0 test_conns =3D trial_conns[i]; >> =C2=A0 =C2=A0 =C2=A0 test_buffs =3D MIN_BUFS_FOR_CONNS(test_conns); >> >> =C2=A0 =C2=A0 =C2=A0 snprintf(cmd, sizeof(cmd), >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0SYSTEMQUOTE "\"%s= \" --boot -x0 %s " >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0"-c max_connectio= ns=3D%d " >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0"-c shared_buffer= s=3D%d " >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0"< \"%s\" > \"%s\= " 2>&1" SYSTEMQUOTE, >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0backend_exec, boo= t_options, >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0test_conns, test_= buffs, >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0DEVNULL, DEVNULL); >=20 > Are you able to compile from source? If so, can you hack this part to > print the value of cmd at this point, so you can see clearly exactly > what it's trying unsuccessfully to do? >=20 > ...Robert >=20 > --=20 > Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-bugs >=20 >=20 --=20 View this message in context: http://old.nabble.com/Failed-to-run-initdb---= not-resolved-bug-5130-tp26996830p27330525.html Sent from the PostgreSQL - bugs mailing list archive at Nabble.com.
pgsql-bugs by date: