Re: add log messages when replication slots become active and inactive (was Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?)
От | Peter Smith |
---|---|
Тема | Re: add log messages when replication slots become active and inactive (was Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?) |
Дата | |
Msg-id | CAHut+PvuKzniJ3U-V+XxGb8m0Cj2gQgtkjW3QPBFYk5GgCyLrg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: add log messages when replication slots become active and inactive (was Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?) (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>) |
Ответы |
Re: add log messages when replication slots become active and inactive (was Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?)
Re: add log messages when replication slots become active and inactive (was Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?) |
Список | pgsql-hackers |
Some minor comments for v17-0001. ====== 1. + ereport(log_replication_commands ? LOG : DEBUG1, + SlotIsLogical(s) + /* translator: %s is name of the replication slot */ + ? errmsg("acquired logical replication slot \"%s\"", + NameStr(s->data.name)) + : errmsg("acquired physical replication slot \"%s\"", + NameStr(s->data.name))); 1a. FWIW, if the ternary was inside the errmsg, there would be less code duplication. ~ 1b. I searched HEAD code and did not find any "translator:" comments for just ordinary slot name substitutions like these; AFAICT that comment is not necessary anymore. ~ SUGGESTION (#1a and #1b) ereport(log_replication_commands ? LOG : DEBUG1, errmsg(SlotIsLogical(s) ? "acquired logical replication slot \"%s\"" : "acquired physical replication slot \"%s\"", NameStr(s->data.name))); ~~~ 2. Ditto for the other ereport. ====== Kind Regards, Peter Smith. Fujitsu Australia
В списке pgsql-hackers по дате отправления: