| From: | shveta malik <shveta(dot)malik(at)gmail(dot)com> |
|---|---|
| To: | Bowen Shi <zxwsbg12138(at)gmail(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org, shveta malik <shveta(dot)malik(at)gmail(dot)com> |
| Subject: | Re: BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG |
| Date: | 2022-12-21 09:06:25 |
| Message-ID: | CAJpy0uAjveViJ_zG7uZndZPRc04MkGOSL0js+w8JYvJ4xwLLMw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Yes using XLOG_XACT_INVALIDATIONS. It reduced the number of invalidations
executed per commandId.
I used pstack. But it was pretty quick, not much chance to see stacks.
No lag seen
on the next insert on subscriber after drop publication, even with
heavier testcase.
thanks
Shveta
On Wed, Dec 21, 2022 at 10:45 AM Bowen Shi <zxwsbg12138(at)gmail(dot)com> wrote:
>
> Hello,
> Thanks for your tests.
>
> >
> > No noticeable lag observed on HEAD with the new mechanism of invalidation.
> >
>
> Does the new mechanism of invalidation mean using
> 'XLOG_XACT_INVALIDATIONS‘ to invalid cache? And did you use perf or
> pstack to watch the walsender process.
>
> thanks
> BowenShi
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2022-12-21 19:06:32 | BUG #17727: A query crashes server process: ... was terminated by signal 7: Bus error / Segmentation Fault |
| Previous Message | Bowen Shi | 2022-12-21 05:15:32 | Re: BUG #17716: walsender process hang while decoding 'DROP PUBLICATION' XLOG |