Duplicate Prepared Statement with Thread#kill

[schneems]

As seen in this stack overflow post http://stackoverflow.com/a/31167112/147390 there is a race condition where a prepared statement in the DB, however the thread that created it is killed before Rails can record the successful statement.

I did some grepping and couldn't find this as an issue on Rails, so I wanted to raise it here. I don't know if there's a good work around, the post mentions using a GUID instead of an integer, that could work, or maybe adding retry logic to prepared statement creation so that it records a495 (or whatever number` is already taken and uses the next in the series.

[matthewd]

See #17607, and more recently #25827

[schneems]

Thanks!