>do you think most common connection poolers would continue to
>work after making this change?
Of course, they should.
There are existing cases when commit responds with an error: deferrable constraints.
There's nothing new except it is suggested to make the behavior of commit/prepare failure (e.g. "can't commit the transaction because...") consistent with other commit failures (e.g. deferred violation).