Why is a connection destroyed when there is an error thrown from the connection handler?

[notcome]

I noticed that if the connection handler throws any error, the connection itself is destroyed:

slonik/packages/slonik/src/factories/createConnection.ts

Lines 185 to 196 in 35543e1

	try {
	result = await connectionHandler(
	connectionLog,
	connection,
	boundConnection,
	clientConfiguration,
	);
	} catch (error) {
	await connection.destroy();
	throw error;
	}

Is this really necessary? It feels wrong when:

1. If we are simply throwing an error to indicate an application logic, that connection must destroyed and recreated.
2. If we are doing a transaction and want to rollback, that connection must be destroyed and recreated.

Shouldn't we only destroy the connection when there is some underlying issue?

[gajus]

I never ran into practical issues with regards to this, and it's been a while since I touched this part of the code. Do you have an example of where this becomes an issue?