Query SET client_min_messages = warning; SET TIME ZONE INTERVAL %s HOUR TO MINUTE running sequentially even when no new connection is opened with the DB

[batflarrow]

In the DB logs I can see the query SET client_min_messages = warning; SET TIME ZONE INTERVAL %s HOUR TO MINUTE being run multiple times. From the code I can see that this query is added every time a new connection is being established with the DB. But from the logs I can see that sometimes these queries are being run sequentially one after the other, and are not paired with some other query. Does this query have any impact on the performance, and should I disable this query completely?
I'm using sequelize version 6.29.0, along with @nestjs/sequelize with version 8.0.0.

Example logs -

2023-11-03 11:23:47.018 IST [577775] LOG:  statement: SET client_min_messages TO warning;SET TIME ZONE INTERVAL '+00:00' HOUR TO MINUTE;
2023-11-03 11:23:47.018 IST [577776] LOG:  statement: SET client_min_messages TO warning;SET TIME ZONE INTERVAL '+00:00' HOUR TO MINUTE;
2023-11-03 11:23:47.066 IST [577778] LOG:  statement: SET client_min_messages TO warning;SET TIME ZONE INTERVAL '+00:00' HOUR TO MINUTE;
2023-11-03 11:23:47.097 IST [577777] LOG:  statement: SET client_min_messages TO warning;SET TIME ZONE INTERVAL '+00:00' HOUR TO MINUTE;
2023-11-03 11:23:47.098 IST [577779] LOG:  statement: SET client_min_messages TO warning;SET TIME ZONE INTERVAL '+00:00' HOUR TO MINUTE;
2023-11-03 11:23:47.099 IST [577780] LOG:  statement: SET client_min_messages TO warning;SET TIME ZONE INTERVAL '+00:00' HOUR TO MINUTE;