Re: Replication slot stats misgivings
От | Masahiko Sawada |
---|---|
Тема | Re: Replication slot stats misgivings |
Дата | |
Msg-id | CAD21AoC9KooaL4L_PQMfnxRcf4fzcx-rGHwMmCnGx-1VShiQew@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Replication slot stats misgivings (Amit Kapila <amit.kapila16@gmail.com>) |
Ответы |
Re: Replication slot stats misgivings
|
Список | pgsql-hackers |
On Wed, Apr 28, 2021 at 6:39 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Wed, Apr 28, 2021 at 12:49 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote: > > > > > > BTW regarding the commit f5fc2f5b23 that added total_txns and > > total_bytes, we add the reorder buffer size (i.g., rb->size) to > > rb->totalBytes but I think we should use the transaction size (i.g., > > txn->size) instead: > > > > You are right about the problem but I think your proposed fix also > won't work because txn->size always has current transaction size which > will be top-transaction in the case when a transaction has multiple > subtransactions. It won't include the subtxn->size. Right. I missed the point that ReorderBufferProcessTXN() processes also subtransactions. > I think we can fix it by keeping track of total_size in toptxn as we > are doing for the streaming case in ReorderBufferChangeMemoryUpdate. > We can probably do it for non-streaming cases as well. Agreed. I've updated the patch. What do you think? Regards, -- Masahiko Sawada EDB: https://www.enterprisedb.com/
Вложения
В списке pgsql-hackers по дате отправления: