Re: Skipping logical replication transactions on subscriber side
От | Amit Kapila |
---|---|
Тема | Re: Skipping logical replication transactions on subscriber side |
Дата | |
Msg-id | CAA4eK1LnjUSJ_ri_RdpRU+g=w92ABXeOVUmP4XNxoq-yyZOqvQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Skipping logical replication transactions on subscriber side (Greg Nancarrow <gregn4422@gmail.com>) |
Ответы |
Re: Skipping logical replication transactions on subscriber side
Re: Skipping logical replication transactions on subscriber side |
Список | pgsql-hackers |
On Thu, Aug 12, 2021 at 5:41 PM Greg Nancarrow <gregn4422@gmail.com> wrote: > > On Thu, Aug 12, 2021 at 9:18 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > > A minor comment on the 0001 patch: In the message I think that using > > > "ID" would look better than lowercase "id" and AFAICS it's more > > > consistent with existing messages. > > > > > > + appendStringInfo(&buf, _(" in transaction id %u with commit timestamp %s"), > > > > > > > You have a point but I think in this case it might look a bit odd as > > we have another field 'commit timestamp' after that which is > > lowercase. > > > > I did a quick search and I couldn't find any other messages in the > Postgres code that use "transaction id", but I could find some that > use "transaction ID" and "transaction identifier". > Okay, but that doesn't mean using it here is bad. I am personally fine with a message containing something like "... in transaction id 740 with commit timestamp 2021-08-10 14:44:38.058174+05:30" but I won't mind if you and or others find some other way convenient. Any opinion from others? -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: