DROP DATABASE and prepared transactions

Brought to you by: andrei_mart, koichi-szk, mason_s, nikkhils, pavanvd

#45 DROP DATABASE and prepared transactions

Milestone: 9.2rc

Status: open

Owner: nobody

Labels: None

Priority (1-5): 2

Est. Days: None

Assigned To: Pavan Deolasee

Updated: 2015-03-15

Created: 2014-12-20

Creator: mason_s

Private: No

When DROP DATABASE is run, it should check for outstanding prepared transactions, and fail if there are some.

If there are prepared transactions, the DROP will succeed on some nodes, and fail on others, causing a database to stay around that cannot be dropped.

Because there may be concurrent activity, we may want to first attempt to lock the database when dropping.

Discussion

Saad Talaat - 2015-03-15

I tried to reproduce the issue. However on prepared transactions it fails pointing out that that database has prepared transactions. Any more info on how to reproduce if the issue still valid?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

DROP DATABASE and prepared transactions

Milestone

Searches

Help

#45 DROP DATABASE and prepared transactions

Discussion