Hold off on AWS Aurora and Postgres until further notice

Re:Hold off on AWS Aurora and Postgres until further notice by kurttheviking on Friday December 29, 2017 @02:20PM (#16031328)

We've been using Postgres on RDS for years and were considering moving to Aurora. I am very curious to know more about the fix and planned remedy.

[ Parent | on HN ]

Re:Hold off on AWS Aurora and Postgres until further notice by sudhirj on Friday December 29, 2017 @02:24PM (#16031355)

Current suspects are GIN index problems, but nothing confirmed yet.

[ Parent | on HN ]

Re:Hold off on AWS Aurora and Postgres until further notice by petergeoghegan on Sunday December 31, 2017 @09:36AM (#16040697)

Per my remarks here, I think that there is an obscure bug in GIN vacuuming that the community has yet to identify:

https://postgr.es/m/CAH2-Wz=GTnAPzEEZqYELOv3h1Fxpo5xhMrBP6aM...

It's possible that this upstream PostgreSQL issue affected you. What is known for sure is that there was a bugfix for GIN, that just missed the latest round of point releases. See:

https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit...

This fix alone could have made all the difference here (though this is a guess). I assume you won't have this fix with Aurora just yet (not sure -- I don't work for Amazon). But, I'd mention this to AWS support if it seems at all relevant. Hopefully they'll get in touch with the community if that's what it is.

Good luck

[ Parent | on HN ]

Re:Hold off on AWS Aurora and Postgres until further notice by sudhirj on Tuesday January 02, 2018 @04:30AM (#16050878)

Thanks, will pass this on.

[ Parent | on HN ]

Re:Hold off on AWS Aurora and Postgres until further notice by kurttheviking on Friday December 29, 2017 @02:25PM (#16031360)

Ugh, that's bad -- sorry to hear that. We GIN index several JSONB fields as well.

[ Parent | on HN ]