[outworlder]

> This is a configurable item, and the idea that everything should always be encrypted all the time may not be true for various use-cases.

Isn't that what 'default' means? When you have exceptions, you can change from the default.

[OrvalWintermute]

Default highly secure is not always the best option when it may severely conflict with usability, or require significant amounts of labor to instantiate.

If the key intention for a downloadable Postgresql is developer productivity, and the intended environment is local on a laptop communicating to a client local there too, then this would make alot more sense.