| From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
|---|---|
| To: | "Andrew Dunstan" <andrew(at)dunslane(dot)net>, "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: windows / initdb oddness |
| Date: | 2006-02-21 15:16:02 |
| Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C805A@algol.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> This took me hours to find ...
>
> On my Windows box, CVS HEAD gets an execution failure on "initdb foo"
> but succeeds happily with "initdb -D foo".
>
> This is not true for REL8_1_STABLE, nor is it true for all
> Windows machines/environments, apparently, otherwise we would
> be seeing failures from the buildfarm member snake, since the
> buildfarm script does "initdb data".
>
> My suspicion is that this is some side effect of the
> restricted-exec patch, but I don't have time to dig further right now.
Um, so what error msg do you get when it's failing?
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-02-21 15:17:02 | Re: pg_config, pg_service.conf, postgresql.conf .... |
| Previous Message | Tom Lane | 2006-02-21 15:15:36 | Re: pg_config, pg_service.conf, postgresql.conf .... |