Hacker Newsnew | past | comments | ask | show | jobs | submit | markporter_aws's commentslogin

Amazon has made contributions to open source in many ways, including bug fixes, spending hundreds of thousands/year to sponsor conferences, and even giving the PostgreSQL community a free testing account to run regression, soak, or functionality test suites on AWS for free. So yes, Amazon contributes cash to open source projects, at least to PostgreSQL, which we find to be a wonderful community that we are proud to be part of.


How much cash did AWS give to Postgres?


It is true that Amazon Aurora is not limited by the bandwidth of the storage system, as it is huge and distributed across hundreds/thousands of nodes across an entire AWS region. And storage for each database instance is indeed only limited to 64TB, far above what most people need. But each single instance can still have limitations, such as CPU horsepower, memory, etc. The r4.16xl has 25Gbit networking, as opposed to the r4.8xl, which has 10Gbit network. So if your workload is write-intensive, such as streaming or IOT data, you will find the r4.16xl can have significantly better write performance. https://aws.amazon.com/ec2/instance-types/ I hope this helps!


Which particular types and combination of CPU/RAM would you like?


At a minimum, I'd like to see something half the size of the r4.large. The current r4.large is definitely bigger than I'd want to use for an experiment with a few users.


Jeff, that makes sense. We're working on it. Thanks for the information!


Which region? We're working very hard to add regions as quickly as possible!


I feel silly asking this, but https://aws.amazon.com/blogs/aws/now-available-amazon-aurora... says "four regions" -- when I go to look at the Aurora price page (https://aws.amazon.com/rds/aurora/pricing/), it lists what looks like more than four.

Which is correct?

What I really want to know is whether I can use this in ap-northeast-1. :)


https://aws.amazon.com/about-aws/whats-new/2017/10/announcin... shows the four regions we are currently available in.

On https://aws.amazon.com/rds/aurora/pricing/, if you go to the "PostgreSQL Compatible" dropdown, you will see those same four regions.

We're working on making that page easier to parse, and the fact that you just ran into this confusion reinforces our committment to fix it - thank you!


Thank you for the understanding response!

I would like to add my vote for looking forward to support in ap-northeast-1 as well, then. :)


Stay tuned!


What instance types would you like to see? T2s? If so, which ones?


My team was hoping for db.t2.small and db.t2.medium so we could compare against similar sized regular Postgres instances.


Thanks for the replies - we're working on smaller instances, though we don't have a date yet!


We are also looking to test the small and medium t2s versus PostgresRDS on small and medium.


Where I work we currently run 2 RDS PostgreSQL Instances in production, one on T2.small and the other T2.medium.

We never run out of CPU credits. We are dying to move to Aurora but the current instance sizes prevent us :( until we fully move away from SQL Server where our load on PostgreSQL will increase, its a huge cost for 0 gain right now.


i have a postgres running on a t2.small in RDS right now


I'm sorry the product team never got back to you. We'll get back to the email you just sent us on the preview thread.

If you have any issues with your bill, let us know and we'll happily look into it. But I'd rather work with you to figure out what went on and get it fixed for you!


Sure thing, feel free to reply to my email. \l+ shows 485 GB, and hitting temp_bytes from pg_stat_database is 0, but billable space is 1050G. I'd like to promote Aurora to production, but some of my system's 'legacy' queries which live behind an ORM are grinding against the Aurora instances. I haven't had need to really investigate/optimize the queries (or even try to pick apart what the ORM is doing) as the performance on the vanilla Postgres RDS instance wasn't was great, but wasn't problematic either, even on the db.t2.large's I'd use in lower environments vs db.r4.large's I'm using with Aurora. It may be that I am just missing something obvious.


I hope that’s what happens too. Another project I work on switched to Aurora for MySQL and it’s been phenomenal.

Really hoping for a similar experience with Postgres.


@omarforgotpwd, @purphase, @tengbretson: We're working on everything you just asked for - thanks for letting us know they are important! @jsmeaton: Which region?


Little old Australia (ap-southeast-2) would be insanely welcome.


Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: