> I think this would all be a nice argument to have when introducing a new > function. But I don't think it's a wart sufficiently big to justify breaking > compatibility.
Yeah, I would side as well with the compatibility argument on this one.
I don't really agree with this. I think breaking compatibility in the next major release makes sense here. We already have pg_log_backend_memory_contexts writing to the log, and
If we end up adding a few more functions called pg_log_something that write to the log file,