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.
I still use MySQL because trying out PostgreSQL recently scared me away. Maybe I was trying the wrong thing but I couldn't get pgAdmin to display my tables. I think I sank most of my afternoon trying unsuccessfully to do something MySQL can do in 5 minutes. I recognize I'm used to MySQL but I was under the impression that because PostgreSQL has a similar syntax (SQL) it wouldn't take too long to pickup.
Amazon RDS for PostgreSQL
71–80 of 246 posts
Re: Amazon RDS for PostgreSQL
#72It doesn't mention which version of PostgreSql. I hope it is 9.3. It's got to be at least 9.2 since it supports the Json datatype.
Re: Amazon RDS for PostgreSQL
#73I 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…
Re: Amazon RDS for PostgreSQL
#74Will 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 fi…
Re: Amazon RDS for PostgreSQL
#75I'd be most curious to know how the performance/dollar ratio stacks up to Heroku's Postgres offering.
I don't actually know whether Heroku can failover across an AZ failure.
Re: Amazon RDS for PostgreSQL
#76Re: Amazon RDS for PostgreSQL
#77Re: Amazon RDS for PostgreSQL
#78I 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…
If you're on a Mac and don't want a menubar icon (I decided this recently), `brew install postgres`, and then write yourself some functions to make starting and stopping easier:
https://github.com/jclem/dotfiles/blob/master/zsh/functions/... https://github.com/jclem/dotfiles/blob/master/zsh/functions/...
Re: Amazon RDS for PostgreSQL
#79This 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/
FYI, it doesn't look your payment modal works on smaller browser windows: https://www.monosnap.com/image/UvJbxMQEwkzqLH5btNJ7a9G6Q ... no visible pay button, and the modal itself scrolls when you scroll the page.
Re: Amazon RDS for PostgreSQL
#80I 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…
Makes it very easy if you are Mac, Debian based shop --- or if you just use vagrant.
Currently this looks like: 1. Make sure we have the version of ruby we want (if not use rvm to install) 2. Make sure our db is installed (if not installed use brew (make sure we have brew) to install it) 3. Create our database and users on the new db server 3. Run rake db:setup