postgresql84 causes kernel panic

[simon@…]

Installed postgresql84 and had it running permanently via supplied launchd plist.

Experienced at least 4 fatal kernel panics over the course of 2-3 days. Stack trace said something about the panic originating from launchd.

So I stopped postgres and unloaded it's plist. It's been 2 days now and no problem.

Here's the ports I was using --

postgresql84 @8.4.4_0 (active) postgresql84-server @8.4.4_0 (active) py26-psycopg2 @2.2.1_0+postgresql84 (active)

I'm on snow leopard 10.6.4 --

Model Name: MacBook Pro

Model Identifier: MacBookPro4,1 Processor Name: Intel Core 2 Duo Processor Speed: 2.4 GHz Number Of Processors: 1 Total Number Of Cores: 2 L2 Cache: 3 MB Memory: 4 GB Bus Speed: 800 MHz Boot ROM Version: MBP41.00C1.B03 SMC Version (system): 1.27f2 Serial Number (system): W882334ZYJX Hardware UUID: 49041086-48A3-5208-BAD1-8BCF8E6C0A07 Sudden Motion Sensor: State: Enabled

[danielluke (Daniel J. Luke)]

Do you have a copy of the panic?

It's also possible that postgres was just using a lot of your RAM, so the OS ended up using a bad portion of RAM that is now sitting idle...

[simon@…]

Seems postgres wasn't the issue, my apologies. It happened again an hour ago, this time I got the three beeps so knew it was probably RAM. Reseated it and it's now OK, touch wood.