Re: undetected deadlock in ALTER SUBSCRIPTION ... REFRESH PUBLICATION
Amit Kapila <amit.kapila16@gmail.com>
From: Amit Kapila <amit.kapila16@gmail.com>
To: Shlok Kyal <shlok.kyal.oss@gmail.com>
Cc: Tomas Vondra <tomas.vondra@enterprisedb.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-12-08T11:45:00Z
Lists: pgsql-hackers
Attachments
- v3-0001-Fix-an-undetected-deadlock-due-to-apply-worker.patch (application/octet-stream) patch v3-0001
On Thu, Dec 7, 2023 at 11:21 AM Shlok Kyal <shlok.kyal.oss@gmail.com> wrote:
>
> > I mean to commit the open transaction at the below place in
> > wait_for_relation_state_change()
> >
> > wait_for_relation_state_change()
> > {
> > ...
> > -- commit the xact
> > WaitLatch();
> > ...
> > }
> >
> > Then start after the wait is over. This is just to test whether it
> > improves the difference in regression test timing.
>
> I tried the above approach and observed that the performance of this
> approach is nearly same as the previous approach.
>
Then let's go with the original patch only. BTW, it took almost the
same time (105 wallclock secs) in my environment (CentOs VM) to run
tests in src/test/subscription both with and without the patch. I took
a median of five runs. I have slightly adjusted the comments and
commit message in the attached. If you are fine with this, we can
commit and backpatch this.
--
With Regards,
Amit Kapila.
Commits
-
Fix an undetected deadlock due to apply worker.
- 8d7d2197f31c 17.0 landed
- 01cc92fa6251 16.2 landed
- 332b43063351 15.6 landed
- 3f86867d560f 14.11 landed
- b47ea4f3d305 13.14 landed
- e81e617f3273 12.18 landed