4 ms·
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, le
by markporter_aws 9y ago
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!
- brightball 9y agoI 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.
- nmilford 9y agoSure 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.