Unprepared Execute False by default > why statements are prepared by default

Unprepared Execute False by default > why statements are prepared by default

Why UnpreparedExecute is *False* by default.

So you always prepare statements by default?
If i understand the help correctly, this will call an additional "PREPARE". (https://www.postgresql.org/docs/current/sql-prepare.html)

This is in most cases not nescesarry and useless (and i think slower than execute the query directly because of additional network calls).

I think standard should be to NOT prepare Statements by default.

If i write a super complex statement that will be executet in the same way many times, than the developer will think about this and activate this.


Additionally there seems some uncelar behavoir if this setting is switched you can see here: