On Fri, Dec 14, 2018 at 4:43 AM Andres Freund <and...@anarazel.de> wrote: > This leads me to think that we possibly should move computation of the > last removed xid from recovery to the primary, during the generation of > the xl_btree_delete WAL record.
Do I understand correctly that we need this xid computation, because we may delete some index tuples using kill_prior_tuple before we prune corresponding heap tuples (which would be also replicated and cause required conflict)? If so, then can we just give up with that? That is before setting kill_prior_tuple = true, prune corresponding heap tuples. ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
