Oh hmm that's interesting! I'm more intrigued as to why you were hitting the statement timeouts, as I often (enough) add indexes to hot tables using the concurrent feature in postgres, and haven't ran into this before I don't think.
Do you guys use the 'disable_ddl_transaction' when doing the concurrent migrations, my understanding was that was necessary but maybe not!
Also not sure if this would have caught it or not, but Ive enjoyed using Strong Migrations to try to catch dangerous migrations early! Though you may have already been following that advice here lol
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.