QuerySet.get() leaves postgres in 'current transaction is aborted...' state if invalid data is passed.

[Asit Kumar Singh]

calling get_object_or_404() with invalid data (e.g. invalid UUID) in any of the fields causes Postgres to stay in the same transaction. On Postgres, this leads to the failure of any new query using the same connection. The reason for this is Postgres on getting invalid input doesn't rollback the transaction automatically and neither does Django explicitly rollbacks such get calls, which leaves the database in an unstable state.
Example code:

     def invalid_data(model):
          try:
                 obj=get_object_or_404(model, id=f"{invalid_data}")
          except:
                 # do something
         model.objects.first().field # this will fail with current transaction is aborted error.
          

[Nayan sharma]

can anyone help me through this as this is going to be my first contribution to Django.

[Mariusz Felisiak]

get_object_or_404() calls QuerySet.get() without anything fancy, so it's not related with its implementation. It looks that you call invalid_data() inside an atomic transaction, in such cases you shouldn't catch exceptions, see ​"Avoid catching exceptions inside atomic!". If it's not the case, please provide a sample Django 3.1+ project that reproduces this issue (Django 2.2 doesn't receive bugfixes anymore).