| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | windows / initdb oddness |
| Date: | 2006-02-21 13:36:48 |
| Message-ID: | 43FB1770.3080209@dunslane.net |
| 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.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2006-02-21 14:27:38 | Re: pg_config, pg_service.conf, postgresql.conf .... |
| Previous Message | Martijn van Oosterhout | 2006-02-21 12:50:24 | Resurrecting some old patches |