It seems like an oversight to me that local_preload_libraries causes a
new log message to appear each time a new connection is established.
Is there any sympathy for the view that we should have a way of
turning this off, or simply not log such messages? We could still have
it appear at DEBUG2 level, as sometimes happens in the EXEC_BACKEND
case (granted, this is just so that there is behavior equivalent to
the !EXEC_BACKEND case for shared_preload_libraries).
--
Peter Geoghegan