On Oct 7, 2011, at 7:39 PM, René Fournier wrote: > Plus, I find Macports makes it easy to automate a server build in one script. > The problem as I see it isn't Macports but my unfamiliarity with Postgresql.
I think it's both ;-) I tried macports for a couple of things and gave up on it. It works for getting dependencies for certain things. Then one day it doesn't work because you're trying a combination that wasn't accounted for, and you now have no idea how all those things you previously installed are configured... But if you can find the pg log, it will usually pretty explicitly tell you why the server is quitting on launch. So you might just need to read those wrapper scripts to see how exactly they invoke postgres. -- Scott Ribe scott_r...@elevated-dev.com http://www.elevated-dev.com/ (303) 722-0567 voice -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
