4 ms·

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.

• sudhirj 9y ago
  Current suspects are GIN index problems, but nothing confirmed yet.
  • kurttheviking 9y ago
    Ugh, that's bad -- sorry to hear that. We GIN index several JSONB fields as well.
  • petergeoghegan 9y ago
    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=GTnAPzEEZqYELOv3h1Fxpo5xhMrBP6aMGEKLKv95csQ@mail.gmail.com 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=commitdiff;h=3b2787e1f8f1eeeb6bd9565288ab210262705b56 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
    • sudhirj 9y ago
      Thanks, will pass this on.