| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Tablesync early exit |
| Date: | 2022-03-16 05:08:36 |
| Message-ID: | CAA4eK1LU59aeLpQD8pW3gaA6dqNW-kqEsn3JcUWqotPiarkLLA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 16, 2022 at 1:16 AM Greg Stark <stark(at)mit(dot)edu> wrote:
>
> This patch has been through five CFs without any review. It's a very
> short patch and I'm assuming the only issue is that it's not clear
> whether it's a good idea or not and there are few developers familiar
> with this area of code?
>
> Amit, it looks like you were the one who asked for it to be split off
> from the logical decoding of 2PC patch in [1]. Can you summarize what
> questions remain here? Should we just commit this or is there any
> issue that needs to be debated?
>
Looking closely at this, I am not sure whether this is a good idea or
not. Responded accordingly.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro Horiguchi | 2022-03-16 05:14:32 | Re: Corruption during WAL replay |
| Previous Message | Amit Kapila | 2022-03-16 05:06:48 | Re: Tablesync early exit |