News for hackers. Stuff that matters.
Re:Handling Growth with Postgres by jpitz on Thursday January 17, 2013 @05:52PM (#5075768)
Terrible, how?
Re:Handling Growth with Postgres by rosser on Thursday January 17, 2013 @07:38PM (#5076301)
Please don't feed the troll. Nothing anyone can say about PostgreSQL will ever make taligent respond with anything but negativity about it.
Re:Handling Growth with Postgres by taligent on Thursday January 17, 2013 @06:24PM (#5075948)
Well there is no official PostgreSQL solution. It's a bunch of third party solutions with varying levels of quality, documentation, support and use.

Every notable PostgreSQL deployment has had to 'roll their own'.

Re:Handling Growth with Postgres by joevandyk on Thursday January 17, 2013 @06:33PM (#5076006)
There is an official pg solution since 9.0.

http://www.postgresql.org/docs/9.2/static/warm-standby.html#...

Re:Handling Growth with Postgres by No1 on Thursday January 17, 2013 @11:23PM (#5077086)
Slony has been around since at least 2004.

It was included in the Postgres source code repository. I always considered that to be a pretty official solution.

Re:Handling Growth with Postgres by taligent on Thursday January 17, 2013 @06:47PM (#5076086)
That is simply master/slave.

Not really suitable for the common scalability issues startups deal with today. Like working in multiple Amazon regions or supporting difference sets of servers.

Re:Handling Growth with Postgres by joevandyk on Thursday January 17, 2013 @07:37PM (#5076294)
I was responding to you saying that there was no official replication method for postgresql. There has been for about 2.5 years.

If you are wanting master-master, look into http://postgres-xc.sourceforge.net.

Re:Handling Growth with Postgres by Xylakant on Friday January 18, 2013 @05:29AM (#5078045)
you're well aware that the for example the couchbase cross-datacenter-replication has it's own share of problems such as "what happens when the same dataset gets modified in both clusters?". IIRC it just drops the older change and keeps the newer version. That may or may not be a problem to you, but for others that might just be the nail in the coffin. Every datastore out there has different trade-off that are acceptable for different use-cases. And postgres has it's own share of tradeoffs, but it works quite nicely for a lot of use-cases.
Re:Handling Growth with Postgres by bretthoerner on Thursday January 17, 2013 @06:40PM (#5076058)
> Well there is no official PostgreSQL solution

Wrong. September of 2010: http://www.postgresql.org/about/news/1235/