News for hackers. Stuff that matters.
Re:PostgreSQL 9.4 Released by atonse on Thursday December 18, 2014 @10:55AM (#8767829)
Great news! I'd love to move over to this from MongoDB for a project that has high uptime requirements. But while I think the JSON will really replace it, does PG have a solution for High Availability (like replica sets) in the works?

I'm newer to Postgres so am not sure. Replica Sets are the killer feature for me, more so than just storing JSON documents. I'd appreciate if someone can chime in. I've done some googling but there seem to be multiple strategies for replication.

Re:PostgreSQL 9.4 Released by arthursilva on Thursday December 18, 2014 @11:24AM (#8767997)
PG has async/sync/hybrid replication for years already. It's not as tooled as MongoDB but there's some tools like http://www.repmgr.org/ to amend it.
Re:PostgreSQL 9.4 Released by internetisthesh on Thursday December 18, 2014 @02:44PM (#8769254)
Every time I look into tools like this they are quite far behind for example AlwaysOn in MSSQL. For example, with PG I have to reseed the original master if it comes back online after an outage. It's as far as I can tell not fully automatic and transparent to me as the guy responsible for managing it. With SQL and elasticsearch+ZooKeeper for example nodes can go up and down without anyone noticing it and me not having to do anything. Is this still a place where PG is behind?
Re:PostgreSQL 9.4 Released by tensor on Thursday December 18, 2014 @03:59PM (#8769577)
Yes and no. There are differences in the data guarantees that something like elastic search and postgresql give. So it's not really appropriate to compare those.

MS SQL does have easier tooling for replication. The setup for postrgresql is complex and it doesn't come with out of the box tools to easily manage failover and recovery as you mention. Progress is being made in making this easier, but it's still mostly in the low level functionality:

https://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_...

https://wiki.postgresql.org/wiki/What%27s_new_in_PostgreSQL_...

Re:PostgreSQL 9.4 Released by amitlan on Thursday December 18, 2014 @08:30PM (#8770739)
> For example, with PG I have to reseed the original master if it comes back online after an outage

pg_rewind[1] is supposed to fix this. It's moving into core for 9.5, by the way.

[1] https://github.com/vmware/pg_rewind

Re:PostgreSQL 9.4 Released by devonnulled on Thursday December 18, 2014 @12:32PM (#8768482)
Hey there. I gave a talk at PGConfNYC '14 earlier this year about our solution to HA using open source solutions. The animations and stuff don't really work too well on Slideshare, but it should point you in the right direction:

http://www.slideshare.net/TeamARIN/building-a-high-availabil...

pgSQL doesn't have anything built in for fencing, failing-over, etc. by default, but by using stuff like Pacemaker, you can get the job done with a little elbow grease.

Re:PostgreSQL 9.4 Released by illumen on Friday December 19, 2014 @09:32AM (#8772326)
Do you have any scripts to set up a cluster for this? Or know where to look?
Re:PostgreSQL 9.4 Released by en4bz on Thursday December 18, 2014 @11:28AM (#8768027)
Did you take a look at Slony-I?

http://slony.info/

Re:PostgreSQL 9.4 Released by tracker1 on Thursday December 18, 2014 @01:32PM (#8768837)
There are some open-source options, and several closed source options for this... parts are closer to baked in with 9.4, but being realistic, you need to defer to a commercial option.

EnterpriseDB pricing for this isn't too bad (about $7k/cpu-socket/year), which is a lot less than MS-SQL, DB2 or Oracle for most uses... but it's imho a feature that should be in the box.

Re:PostgreSQL 9.4 Released by jsmeaton on Thursday December 18, 2014 @08:45PM (#8770771)
Pricing per socket really really frustrates me. I work in an Oracle shop where we're hamstrung by similar pricing.
Re:PostgreSQL 9.4 Released by gfodor on Thursday December 18, 2014 @12:04PM (#8768283)
AFAIK RDS has turnkey read only replicas (and hot standby.)