this is awesome!
still, i miss one essential feature - compared to mysql on aws and heroku/postgres: there is no replication for read replicas. yes, you can deploy a "hot standby" replica in another availability zone for failover, but you cant read from it.
Amazon RDS for PostgreSQL
31–40 of 246 posts
Re: Amazon RDS for PostgreSQL
#32Will anyone please explain the tactical reasons why PostgreSQL won? It's pretty obvious it has. I've basically ignored the database wars for a few years, so it's kind of interesting to see that everyone's using PostgreSQL now.
Some engineers I worked with went and interviewed people at various San Francisco startups about their experiences with their databases.
The MySQL startups tended to say "We love MySQL. We've gotten in the habit of taking an hour or two of downtime in the middle of the night every week to run all of our schema migrations, and we've had to build our process around that, but one we had it in place, everything's been fine."
The PostgreSQL startups said "We love PostgreSQL. We run schema migrations in real-time during the middle of our workday, and we don't have any problems."
Re: Amazon RDS for PostgreSQL
#33I've heard about PostgreSQL and know that HN community raves about it, but am currently using RDS with MySQL. Does it make sense to migrate to PostgreSQL, I don't have a lot of data as I'm in the early stage? What are the primary advantages that PostgreSQL provides over MySQL? Any advise/pointers is appreciated.
(Disclaimer: I'm a postgres community member.)
I think the biggest advantages are trust and flexibility.
Trust, because PostgreSQL language semantics are cleaner, closer to the SQL standard, and less likely to surprise you. And postgresql just has a good reputation for traditional engineering quality.
Flexibility, because it offers a lot of APIs and features that can be very useful to adapt your application as needs change. You don't have to go crazy with features, but even simple apps can benefit a lot from prudent use of them -- a trigger here, a foreign table there, or LISTEN/NOTIFY (for cache invalidation) can just save you a huge amount of work and make the system more robust overall. The extension mechanism is very powerful.
Before making any big decisions, do a trial migration and see what you think.
Re: Amazon RDS for PostgreSQL
#34this is awesome! still, i miss one essential feature - compared to mysql on aws and heroku/postgres: there is no replication for read replicas. yes, you can deploy a "hot standby" replica in another availability zone for failover, but you cant read from it.
You can be sure that that will come.
Re: Amazon RDS for PostgreSQL
#35I've heard about PostgreSQL and know that HN community raves about it, but am currently using RDS with MySQL. Does it make sense to migrate to PostgreSQL, I don't have a lot of data as I'm in the early stage? What are the primary advantages that PostgreSQL provides over MySQL? Any advise/pointers is appreciated.
> Does it make sense to migrate to PostgreSQL, I don't have a lot of data as I'm in the early stage? What are the primary advantages that PostgreSQL provides over MySQL? Any advise/pointers is appreciated. If MySQL works for you, there is no reason to change. Some people have quite a dependency on Postgres (hstore, JSON, transactional DDL, pubsub, PLPGSQL etc.)
Ordinarily I would agree, but in this case, the poster said that there's not a lot of data yet so it would be easier to migrate. Choosing a database is a pretty major decision with long-term impact that might not be obvious now, so it's worth exploring a few options if you have that luxury.
I think there are two times when it makes sense to consider a DB migration: (1) early on, when it's easy; (2) if you are in major trouble with your existing DB.
Re: Amazon RDS for PostgreSQL
#36Will anyone please explain the tactical reasons why PostgreSQL won? It's pretty obvious it has. I've basically ignored the database wars for a few years, so it's kind of interesting to see that everyone's using PostgreSQL now.
What has it won?
Re: Amazon RDS for PostgreSQL
#37I've heard about PostgreSQL and know that HN community raves about it, but am currently using RDS with MySQL. Does it make sense to migrate to PostgreSQL, I don't have a lot of data as I'm in the early stage? What are the primary advantages that PostgreSQL provides over MySQL? Any advise/pointers is appreciated.
[deleted]
Re: Amazon RDS for PostgreSQL
#38We've moved off AMZN for more custom hosting. But this is a big win for open source devs. More deoployment options is always a good thing.
Re: Amazon RDS for PostgreSQL
#39How does this compare to Heroku's PG offering?
Good question. Heroku offers an RDS plugin now only for mysql: https://devcenter.heroku.com/articles/amazon_rds
If/when a Heroku RDS plugin for Postgresql arrives, competing benchmarks, a cost calculator, pros and cons would be very interesting, indeed.
Heroku pricing: https://addons.heroku.com/heroku-postgresql
Amazon pricing: http://aws.amazon.com/rds/postgresql/
Re: Amazon RDS for PostgreSQL
#40This is HUGE! I'm using the AWS stack for http://www.soundslice.com/ and I've been using MySQL instead of Postgres, purely because my hatred for MySQL is less than my hatred for being a sysadmin. It was a tradeoff, and I miss Postgres dearly every time I use MySQL. This new Amazon offering solves that. I wrote a little more about my AWS setup here: http://www.holovaty.com/writing/aws-notes/
Let me just say that I absolutely love soundslice. It's a great application!