Plain defaults. Loopback bind keeps the built-in plomid/plomid pair valid; everything else enforces the production posture (100 connections, 30 s statements, 60 s idle transactions, bounded COPY/prepared/portal state) so code that passes locally behaves the same remotely.
plomid-server --data ./dataLoosen timeouts per session while iterating (SET statement_timeout = 0 for a long backfill), never by changing the server flags — the flags are the posture the deploy will run. effective_config at startup shows what is actually in force.
Was this page helpful? Thanks — noted locally, nothing is sent anywhere.