Re: Logical replication origin tracking fix
| От | Peter Eisentraut |
|---|---|
| Тема | Re: Logical replication origin tracking fix |
| Дата | |
| Msg-id | 69ff9da5-0ebc-cadd-c405-997349370b51@2ndquadrant.com обсуждение |
| Ответ на | [HACKERS] Logical replication origin tracking fix (Petr Jelinek <petr.jelinek@2ndquadrant.com>) |
| Список | pgsql-hackers |
On 3/24/17 10:48, Petr Jelinek wrote: > On 10/03/17 05:59, Petr Jelinek wrote: >> while discussing with Craig issues around restarting logical replication >> stream related to the patch he posted [1], I realized that we track >> wrong origin LSN in the logical replication apply. >> >> We currently track commit_lsn which is *start* of commit record, what we >> need to track is end_lsn which is *end* of commit record otherwise we >> might request transaction that was already replayed if the subscription >> instance has crashed right after commit. >> >> Attached patch fixes that. >> > > Rebase after table copy patch got committed. committed -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: