-
Over the next few days, we will be getting this site caught back up with the main site. The last couple of releases have not been updated here in a timely manner, largely because the change in the File Release System on Sourceforge was causing too many headaches. That has been resolved and this will be updated.
2009-11-18 15:16:40 UTC by hawkmoon
-
Over the next few days, we will be getting this site caught back up with the main site. The last couple of releases have not been updated here in a timely manner, largely because the change in the File Release System on Sourceforge was causing too many headaches. That has been resolved and this will be updated.
2009-11-18 15:16:27 UTC by hawkmoon
-
hawkmoon committed revision 239 to the PostgreSQL Tools for MacOS X SVN repository, changing 4 files.
2009-11-18 15:13:03 UTC by hawkmoon
-
Yep, this is memory leak, a release has been added to the SVN code.
2009-11-18 15:11:15 UTC by hawkmoon
-
hawkmoon committed revision 238 to the PostgreSQL Tools for MacOS X SVN repository, changing 2 files.
2009-11-18 15:10:31 UTC by hawkmoon
-
No worries, that's what we don't get paid for :-).
2009-11-02 02:28:42 UTC by hawkmoon
-
and a (belated) big thanks, btw!
2009-11-02 01:53:45 UTC by dvrooman
-
That seems to have done the trick (no error message after a reboot). If it helps you out for future installers, I believe I had installed 8.4.0 in Snow Leopard before I realized it wasn’t compatible yet. I tried thoroughly uninstalling everything, but maybe I missed something.
2009-11-01 19:33:50 UTC by dvrooman
-
sudo chmod 755 /Library/StartupItems/PostgreSQL
sudo chmod 755 /Library/StartupItems/PostgreSQL/PostgreSQL
sudo chmod 644 /Library/StartupItems/PostgreSQL/StartupParameters.plist
sudo chown -R root:wheel /Library/StartupItems/PostgreSQL
The above should fix the startup item to properly start.
2009-11-01 18:44:01 UTC by hawkmoon
-
That certainly explains the problem, but not how it got set that way.
The problem is the ownership and permissions on the startup item.
It looks like the Apple installer used permissions that don't match what they were set to. That said, we are adding some scripting to the end of the installer to force things to a proper permission. I'll lpost when that is available.
2009-11-01 15:03:52 UTC by hawkmoon
