PostgreSQL problems on Mac Yosemite Beta

[pasisiauses]

I already done that. Mike (the other Mike) already looking to the issue, I replied him with things he needed. Waiting for his respond.

[kraada]

Thanks. We'll get this figured out

[d0nkkk]

I submitted a support ticket as well.

How long do these things typically take to get sorted out? I need to know whether it makes sense to revert to mavericks or secure a secondary cpu to run pt4 on.

[runlikeyum]

+1 for the exact same issue

[d0nkkk]

Update:
I created a new database and am now able to use pokertracker (on the new database). However, I still am unable to access/activate the existing database that contains all my previous hands.

[WhiteRider]

Update:
I created a new database and am now able to use pokertracker (on the new database). However, I still am unable to access/activate the existing database that contains all my previous hands.

Thanks for the update. That sounds like a problem with PostgreSQL in the Yosemite update. Bear in mind that OSX 10.10 is a very new Beta and will still have bugs.
Did you make a Backup of your databases before you upgraded your operating system? If so, try restoring the backup as that may well work.

[YashN]

Had a similar issue with Yosemite beta and PT4. This is what I did to make PT4 run again:

Get the latest PostgreSQL installer for Mac OS X and install it. Create a new DB in PT 4.

If you want to be able to access your previous DB, then I recommend exporting/backing up the old DB and re-importing/restoring with Yosemite.

That should work for PT3 too.

[golovinster]

have same problem. trying to run PGSL manually and get that message:
2014-08-04 11:02:14 YEKT FATAL: could not create shared memory segment: Invalid argument
2014-08-04 11:02:14 YEKT DETAIL: Failed system call was shmget(key=5432001, size=37969920, 03600).
2014-08-04 11:02:14 YEKT HINT: This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMMAX parameter. You can either reduce the request size or reconfigure the kernel with larger SHMMAX. To reduce the request size (currently 37969920 bytes), reduce PostgreSQL's shared_buffers parameter (currently 4096) and/or its max_connections parameter (currently 104).
If the request size is already small, it's possible that it is less than your kernel's SHMMIN parameter, in which case raising the request size or reconfiguring SHMMIN is called for.
The PostgreSQL documentation contains more information about shared memory configuration.

[kraada]

Open Terminal and run this command and let me know if it fixes things (it's a temporary measure until the next reboot, until we find a working value there's no reason to change it permanently):

sudo sysctl -w kern.sysv.shmmax=75939840

[golovinster]

already run this command with 1G value. but no result
new postgres 9.3 installation works well.