Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Amazon RDS for PostgreSQL

aws.amazon.com

Post reply on HN
Print view View original

81–90 of 246 posts

Re: Amazon RDS for PostgreSQL

#81

Post by shaunrussell »

Keyframe wrote: post #47
natural219 wrote: post #41

I hate PostgreSQL. Yes, I am a dummy application developer who doesn't understand database software. Every time I try to install PostgreSQL it fails. Every time I install MySQL it installs successfully with no problems. Actually, that's the extent of my experience with it, and I guess I'm fine dealing with a database that doesn't validate date formats strictly if I can use the damn database without hassle . I am tota…

Yeah, psql is really hard to install. For example on ubuntu: apt-get install postgresql postgresql-contrib Who could install this nonsense??

He is probably using Windows.

Re: Amazon RDS for PostgreSQL

#82

Post by shaunrussell »

natural219 wrote: post #41

I hate PostgreSQL. Yes, I am a dummy application developer who doesn't understand database software. Every time I try to install PostgreSQL it fails. Every time I install MySQL it installs successfully with no problems. Actually, that's the extent of my experience with it, and I guess I'm fine dealing with a database that doesn't validate date formats strictly if I can use the damn database without hassle . I am tota…

Your loss!

Re: Amazon RDS for PostgreSQL

#83

Post by craigkerstiens »

josephlord wrote: post #75
frakkingcylons wrote: post #13

I'd be most curious to know how the performance/dollar ratio stacks up to Heroku's Postgres offering.

From a very quick glance at the small end the Amazon options are a little more than half the price (Ireland single AZ instance pricing and even less reserved) but multi-AZ options are probably very similar. I don't actually know whether Heroku can failover across an AZ failure.

disclaimer: Heroku PM here

By default our followers and HA is automatically cross AZ. You also have an ability to create followers across region, but we do not automatically failover on those due to latency.

Re: Amazon RDS for PostgreSQL

#84

Post by vec »

pbreit wrote: post #54
sillysaurus2 wrote: post #12

Will 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.

Hmmm...I was wondering why MySQL is still much more widely used.

Inertia, largely. Postgres is more scalable and has quite a few nonstandard additions that are insanely useful from time to time, but it's not always a drop-in MySQL replacement. If you're just writing something simple like a blog or CMS then you don't need the extra functionality.

Plus Wordpress has a hard requirement for MySQL, and like it or not a huge number of projects still use it as a framework.

Re: Amazon RDS for PostgreSQL

#86

Post by maaku »

smileysteve wrote: post #74
jes5199 wrote: post #32

Earlier quoted context omitted.

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 fi…

Very important to note that MySQL 5.6 has ONLINE ALTER.

Is it transactional?

Re: Amazon RDS for PostgreSQL

#87

Post by fdr »

josephlord wrote: post #75
frakkingcylons wrote: post #13

I'd be most curious to know how the performance/dollar ratio stacks up to Heroku's Postgres offering.

From a very quick glance at the small end the Amazon options are a little more than half the price (Ireland single AZ instance pricing and even less reserved) but multi-AZ options are probably very similar. I don't actually know whether Heroku can failover across an AZ failure.

> From a very quick glance at the small end the Amazon options are a little more than half the price (Ireland single AZ instance pricing and even less reserved) but multi-AZ options are probably very similar.

Did you add disk? People seldom do, I can attest it's a big part of the bill...

> I don't actually know whether Heroku can failover across an AZ failure.

"Followers" have preferred another AZ for quite some time -- almost since the beginning -- and Heroku Postgres HA is based on similar technology. So, yes.

Re: Amazon RDS for PostgreSQL

#88

Post by amock »

MrGando wrote: post #11
runako wrote: post #10

Earlier quoted context omitted.

MySQL (free) and Oracle BYOL (no additional license cost) are the same cost at RDS. Since PG is free, I'd guess the cost will be the same as MySQL.

That's what I think too, they should state MySQL/PostgreSQL or something like that in the calculator though.

PostgreSQL costs more than MySQL according to http://aws.amazon.com/rds/pricing/ .

Re: Amazon RDS for PostgreSQL

#89

Post by falcolas »

bsaul wrote: post #73
falcolas wrote: post #67

I have but one suggestion. Unless RDS for PostgreSQL is drastically different from RDS for MySQL, you still need a DB administrator. RDS removes remarkably little of the pain of running a database instance (most of the pain that's removed is just the up front setup), and ends up adding a lot of inconveniences for your day-to-day operations. Also don't count on their replication as your backup. OK. That's two suggesti…

Any link to a page providing more info on those quircks ? I'm deciding between a traditionnal ec2 instance running postgres or rds at the very precise moment !

The long and short of it is that you do not have an account with super access (you can't perform normal actions like killing threads, viewing processlists, change variables, etc). You instead have to use special stored procedures to perform basic administrative functions.

Also, you can't take advantage of replication (aside from their own read replicas within other RDS instances) or binary backups. Anything that requires access to the machine itself is impossible except through Amazon's support channels.

Its gotten better than it was, but it's still a headache to monitor and manage as a DBA.

Re: Amazon RDS for PostgreSQL

#90

Post by ChikkaChiChi »

adrianh wrote: post #23
yumraj wrote: post #8

I'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.

Postgres actually cares about your data. Perhaps you mistakenly insert "2013-10-32" into a date column. MySQL will silently convert this to "0000-00-00" (!!). Postgres will raise an error. Perhaps you make an error in a transaction. MySQL lets you keep doing subsequent things in the transaction. Postgres treats the transaction as invalid and forces you to start over. Perhaps you want to add a column to a table that h…

I've rarely seen a "Why not X?" so concise in getting its point across. Thanks!
Post reply on HN