On 2025-Oct-03, Peter Smith wrote: > Summary > > The idea to change the pg_log_info macro globally seems risky. There > are 400+ usages of this in the PG code, way beyond the scope of these > few tools that have a dry-run.
Ok. > So, that makes pg_createsubscriber the odd man out. Instead of > introducing a new logging macro, perhaps it's better (for code > consistency) just to change pg_createsubscriber to use that same > logging pattern. Sure, let's go that way. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
