| From: | Keisuke Kuroda <keisuke(dot)kuroda(dot)3862(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables |
| Date: | 2020-09-28 02:20:42 |
| Message-ID: | CANDwggLRTUXSHk0VCRFX__aqthRB1L5xmXSvK4a-g45k4A7OHg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi Amit,
Thank you for the reply!
> However, after commit c55040ccd0 (When wal_level=logical,
> write invalidations at command end into WAL so that decoding can use
> this information.) we actually know exactly when we need to execute
> each invalidation.
I see, thank you for your explaination.
I'll try to think about the solution by using XLOG_INVALIDATIONS
and referring to the thread
"PATCH: logical_work_mem and logical streaming of large in-progress
transactions".
Best Regards,
Keisuke Kuroda
NTT Software Innovation Center
keisuke(dot)kuroda(dot)3862(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2020-09-28 02:31:42 | Re: Feature improvement of tab completion for DEALLOCATE |
| Previous Message | Tom Lane | 2020-09-28 01:58:43 | Re: Small improvements to pg_list.h's linitial(), lsecond(), lthird() etc macros |