Commitdd4ab6f

Amit Kapila

committed

Fix the check to limit sync workers.

We don't allow to invoke more sync workers once we have reached the syncworker limit per subscription. But the check to enforce this also doesn'tallow to launch an apply worker if it gets restarted.This code was introduced by commitde43897 but we caught the problemonly with the test added by recent commitc91f71b which started failingoccasionally in the buildfarm.As per buildfarm.Diagnosed-by: Amit Kapila, Masahiko Sawada, Tomas VondraAuthor: Amit KapilaBackpatch-through: 10Discussion:https://postgr.es/m/CAH2L28vddB_NFdRVpuyRBJEBWjz4BSyTB=_ektNRH8NJ1jf95g@mail.gmail.com https://postgr.es/m/f90d2b03-4462-ce95-a524-d91464e797c8@enterprisedb.com

1 parent587de22 commitdd4ab6fCopy full SHA for dd4ab6f

File tree

-4

lines changed

-4

lines changed

Lines changed: 4 additions & 4 deletions

Original file line number	Diff line number	Diff line change
`@@ -344,11 +344,11 @@ logicalrep_worker_launch(Oid dbid, Oid subid, const char *subname, Oid userid,`
`344`	`344`	`}`
`345`	`345`
`346`	`346`	`/*`
`347`		`- *If we reached thesyncworker limit per subscription, just exit`
`348`		`- *silently as we might get here because of an otherwise harmless race`
`349`		`- * condition.`
	`347`	`+ *We don't allow to invoke moresyncworkers once we have reached the sync`
	`348`	`+ *worker limit per subscription. So, just return silently as we might get`
	`349`	`+ *here because of an otherwise harmless racecondition.`
`350`	`350`	`*/`
`351`		`-if (nsyncworkers >=max_sync_workers_per_subscription)`
	`351`	`+if (OidIsValid(relid)&&nsyncworkers >=max_sync_workers_per_subscription)`
`352`	`352`	`{`
`353`	`353`	`LWLockRelease(LogicalRepWorkerLock);`
`354`	`354`	`return;`

Comments

(0)