Re: Resetting spilled txn statistics in pg_stat_replication
От | Amit Kapila |
---|---|
Тема | Re: Resetting spilled txn statistics in pg_stat_replication |
Дата | |
Msg-id | CAA4eK1J8DCKFfFMdn4Zf5eAhkPpPCi0TmfNp1FgFDxPsFSPYLQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Resetting spilled txn statistics in pg_stat_replication (Amit Kapila <amit.kapila16@gmail.com>) |
Список | pgsql-hackers |
On Tue, Oct 13, 2020 at 12:42 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Tue, Oct 13, 2020 at 12:17 PM Masahiko Sawada > <masahiko.sawada@2ndquadrant.com> wrote: > > > > I agree to check if the spill_counts and spill_txns are positive. > > > > I am able to reproduce this problem via debugger. Basically, execute > the Insert mentioned above from one the psql sessions and in > ExecInsert() stop the execution once 'estate->es_processed > 4000' and > then from another psql terminal execute some DDL which will be ignored > but will any try to decode commit. /will any try to decode commit./we will anyway try to decode commit for this DDL transaction when decoding changes via pg_logical_slot_peek_changes > Then perform 'continue' in the > first session. This will lead to inconsistent stats value depending > upon at what time DDL is performed. I'll push the patch as I am more > confident now. > -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: