Oh dear god yes. I just rigged up a PostgreSQL instance on Ec2 for a new project, so excited to shut it down and let amazon deal with it. Hell yes.
Amazon RDS for PostgreSQL
91–100 of 246 posts
Re: Amazon RDS for PostgreSQL
#92Will 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.
Unfortunately things that take 5 minutes in a complex application typically required an order of magnitude larger investment up front in manual reading and experience.
Re: Amazon RDS for PostgreSQL
#93Earlier quoted context omitted.
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.
Can you elaborate further?
Coming from a MySQL background, I sort-of assumed PostgreSQL worked the same way. I remember after setting up the server, pgAdmin was very difficult to navigate. I managed to get a database and table made and got some data in (using SQL) but I couldn't view any of the data. Compared to MySQL + Sequel Pro it was very difficult to use for a beginner.
Postgres is very powerful and can do a lot. I think I just need a good tutorial and some time to get used to it.
Re: Amazon RDS for PostgreSQL
#94I 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…
As someone who is familiar with the rigamarole of PCI compliance, I respectfully disagree.
Disagree with what? Keeping your own backups? Probably not - if you're not keeping offsite backups, you're begging to go out of business.
With needing a DBA, even if you're still on RDS? I don't see what that has to do with PCI compliance.
With RDS only removing the up-front setup pain, at the cost of ongoing maintenance... as someone who is also familiar with PCI (and HIPPA, and DOD) compliance, I respectfully disagree with your disagreement (well, if you're working with DOD, AWS isn't even an option to begin with).
Given the choice to run my own instance of a DB on a AWS instance (which carries the same certifications as RDS), and use RDS, I will run my own instance every time. The setup just isn't onerous enough to justify the daily productivity cost.
Re: Amazon RDS for PostgreSQL
#95Great news and for people who ask them-self the questions but the version is Pg 9.3.1. Not all Pl are available, and it misses the PL/V8 and PL/Python at least. And it seems that all fdw (Foreign Data Wrapper) extensions are missing. But it's a great start, I'm looking forward to try. If anybody know if we can still access the WAL log then it will be very useful http://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/C…
PL/Python is very unlikely to appear soon unfortunately because it is an untrusted language in PostgreSQL. EDIT: you are right, PL/Python is supported as well. I only read the "Language Extensions :PL/Perl, PL/pgSQL, PL/Tcl" part at the top.
quote: "Three language extensions are included with PostgreSQL to support Perl, Python and Tcl"
Re: Amazon RDS for PostgreSQL
#96I 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…
sudo apt-get install postgresql
Re: Amazon RDS for PostgreSQL
#97Note that AWS' PostgreSQL offering is more expensive than its MySQL counterpart.
Re: Amazon RDS for PostgreSQL
#98This 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!
Thanks! And it'll be even better once I migrate to Postgres. :-)
Re: Amazon RDS for PostgreSQL
#99Earlier quoted context omitted.
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.
Can you please explain the value proposition of using Heroku Postgres vs RDS now?
Heroku's solution is 2 to 4 times more expensive for the same type of DB, and RDS even allows for reserved instances to further lower the bill.
Re: Amazon RDS for PostgreSQL
#100Will 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…
pt-online-schema-change from Percona addresses this particular point with MySQL nicely for us, incidentally. We use their Percona XtraDB Cluster fork and are quite happy.