Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
| От | Amit Kapila |
|---|---|
| Тема | Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables |
| Дата | |
| Msg-id | CAA4eK1KU17W=s9=P0VR23LHx2jr4vwtryj1A1jKuowcN8xTz4g@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables (Keisuke Kuroda <keisuke.kuroda.3862@gmail.com>) |
| Ответы |
Re: Logical replication CPU-bound with TRUNCATE/DROP/CREATE many tables
|
| Список | pgsql-hackers |
On Mon, Sep 28, 2020 at 7:50 AM Keisuke Kuroda <keisuke.kuroda.3862@gmail.com> wrote: > > 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 > You need to refer to XLOG_XACT_INVALIDATIONS, not XLOG_INVALIDATIONS. > and referring to the thread > "PATCH: logical_work_mem and logical streaming of large in-progress > transactions". > Okay. Feel free to clarify your questions if you have any? Are you interested in writing a patch for the same? -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: