ProzacBlues

Down & Brown
since 1998

Getting Leopard Licked: installing postgres82 with MacPorts

Without a doubt the most challenging unix-on-a-mac-like thing I've had to do is install the Postgres database server on my MacBook Pro. I persisted with the MacPorts approach (I like MacPorts, any package manager is a good thing) and finally found a solution that
worked for me.
I say this because there are many legitimate solutions out there... the trick is finding one that works for you.

One of the most ironical things about this, is that in one of my final emails at Yamaha Music went along the lines of, "... do not do this. It won't work. Not even if you try twice." I tried some of these solutions, over and over again, crossing fingers and waving dead chickens around hoping that by the glory of geebers, something would work.

The first discovery was that there is a
MacPorts ticket
for the problems I was encountering - this details are similar to the grief I was having, but not the same.

Further Google searches on the problem revealed some helpful advice from Lee Packam's blog; he had a handy post describing the same kinda problem, but with a
specific patch for DTrace
and that configurable option.

I tried this several times yesterday, blindingly hoping that it was something I was doing wrong. The unix side of Mac
is
was so unfamiliar to me that I didn't have a clue what I was doing.

Today I came accross
Jeffrey Gelens post,
who was also unable to build using the Packam DTrace fix, but with some twiddling came up with a solution that worked for him. I tried this a couple of times (to be sure) and still it didn't work.

This technique combines the previous two in a sensible way, kinda - if you read and look closely, you'll notice that the DTrace patch is probably not required, furthermore, by this time the MacPorts guys had updated the Postgres PortFile to include the Packam DTrace Patch anyway. I'm just not certain that this guy even bothered to include it in his configure command.

Anyhoo, I'm relieved to finally have it installed and working.

Why bother? You might also ask; well, as one of my new colleagues suggested, if possible my applications should be database platform independent -- which makes sense. So I
did
have MySQL 5 running by yesterday evening.

All in all, a painful experience. I probably would have been much, much easier if I'd waited for a month or two - hell, even a couple of weeks for the MacPort weenies to have sussed it out.