Re: Conflict Detection and Resolution
| От | Dilip Kumar |
|---|---|
| Тема | Re: Conflict Detection and Resolution |
| Дата | |
| Msg-id | CAFiTN-vqRi0kazq0Kh75CP79NFK+4QGUcKD6Eavu37zqPwLmAA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Conflict Detection and Resolution (Amit Kapila <amit.kapila16@gmail.com>) |
| Ответы |
Re: Conflict Detection and Resolution
Re: Conflict Detection and Resolution |
| Список | pgsql-hackers |
On Tue, Jun 4, 2024 at 9:37 AM Amit Kapila <amit.kapila16@gmail.com> wrote: > > Can you share the use case of "earliest_timestamp_wins" resolution > method? It seems after the initial update on the local node, it will > never allow remote update to succeed which sounds a bit odd. Jan has > shared this and similar concerns about this resolution method, so I > have added him to the email as well. > I can not think of a use case exactly in this context but it's very common to have such a use case while designing a distributed application with multiple clients. For example, when we are doing git push concurrently from multiple clients it is expected that the earliest commit wins. -- Regards, Dilip Kumar EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: