Re: Conflict detection for update_deleted in logical replication
От | Amit Kapila |
---|---|
Тема | Re: Conflict detection for update_deleted in logical replication |
Дата | |
Msg-id | CAA4eK1KKvBs5aaXC5kZ64LX7124-XcZE5wchgPQugBtLJZwnZQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Conflict detection for update_deleted in logical replication (shveta malik <shveta.malik@gmail.com>) |
Список | pgsql-hackers |
On Thu, Aug 14, 2025 at 9:02 AM shveta malik <shveta.malik@gmail.com> wrote: > > On Wed, Aug 13, 2025 at 5:42 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > > > > > > > 4) > > > For the DETAIL part of resume and stop messages, how about these: > > > > > > The retention duration for information used in conflict detection has > > > exceeded the limit of xx. > > > The retention duration for information used in conflict detection is > > > now within the acceptable limit of xx. > > > The retention duration for information used in conflict detection is > > > now indefinite. > > > > > > > Similar to the previous point, will it be better to keep it short by > > using "conflict detection info", for example, it will lead to message > > like "The retention duration for conflict detection info is now > > indefinite."? > > > > Works for me as I understand the context. But could it be confusing > for users? Could it be inferred as info about conflicts rather than > info used while detecting conflicts? > Fair point. We can retain your proposed message. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: