Is the database working as expected?

#meta #postgres

If you are reading this, the answer is yes.

We just updated our Postgres version, so I'm thankful nothing went wrong.

Top comments (20)

rhymes • Oct 16 '19 • Edited

I'm so happy we've upgraded to PostgreSQL 11, I can finally start using all the features under the sun ☀️

😂

Renato Byrro • Oct 16 '19 • Edited

Some features were down (now good) for a few minutes:

Dashboard inaccessible
Wouldn't save changes to an article
Unpublished articles were not accessible (reading draft or editing)

Yes, guilty, I'm a heavy user and needed all this during your 2-minute migration window 😊

Ben Halpern • Oct 16 '19

We could have optimized for a time where we had less traffic, like late Friday night, but since we hadn't performed this kind of upgrade before we felt like optimizing for a time where most of the team could be online and alert made sense.

The next time we need scheduled downtime (or, gasp! face unscheduled downtime) we will likely have way more users online at all times. This kind of thing isn't getting easier.

K • Oct 16 '19

Fortnite style!

Renato Byrro • Oct 16 '19

No worries at all 😉 👍

Was only reporting because I thought it could make it easier for you guys to track any improvement opportunities

rhymes • Oct 16 '19

I know, but Heroku prudently keeps that for 3 months in beta.

I guess we'll have to upgrade again next year :P

KP • Oct 16 '19

Just curious why dev is using postgres vs mysql. What are the benefits?

Emilie Gervais • Oct 16 '19

workin' ;)

KP • Oct 17 '19

Thanks for the detailed explanation! I don't come from the ROR community so Postgres is foreign to me...and I know a lot of people that fall inthe same boat. Your answer was helpful, so thanks.