From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
---|---|
To: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "tanghy(dot)fnst(at)fujitsu(dot)com" <tanghy(dot)fnst(at)fujitsu(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>, Greg Nancarrow <gregn4422(at)gmail(dot)com>, "houzj(dot)fnst(at)fujitsu(dot)com" <houzj(dot)fnst(at)fujitsu(dot)com>, "osumi(dot)takamichi(at)fujitsu(dot)com" <osumi(dot)takamichi(at)fujitsu(dot)com>, Alexey Lesovsky <lesovsky(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Skipping logical replication transactions on subscriber side |
Date: | 2022-01-27 13:42:19 |
Message-ID: | cfcc839b-0851-4112-a7c5-1543d129e811@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 26.01.22 05:05, Masahiko Sawada wrote:
>> I think it is okay to clear after the first successful application of
>> any transaction. What I was not sure was about the idea of giving
>> WARNING/ERROR if the first xact to be applied is not the same as
>> skip_xid.
> Do you prefer not to do anything in this case?
I think a warning would be sensible. If the user specifies to skip a
certain transaction and then that doesn't happen, we should at least say
something.
From | Date | Subject | |
---|---|---|---|
Next Message | Amul Sul | 2022-01-27 13:45:34 | Re: generalized conveyor belt storage |
Previous Message | Tomas Vondra | 2022-01-27 13:40:54 | Re: BRIN summarization vs. WAL logging |