forked frompostgres/postgres
- Notifications
You must be signed in to change notification settings - Fork6
Commit0e0f6e2
Reload configuration more frequently in apply worker.
The apply worker was not reloading the configuration while processingmessages if there is a continuous flow of messages from upstream. It wasalso not reloading the configuration if there is a change in theconfiguration after it has waited for the message and before receiving thenew replication message. This can lead to failure in tests because weexpect that after reload, the behavior of apply worker to respect thechanged GUCs.We found this while analyzing a rare buildfarm failure.Author: Hou ZhijieReviewed-by: Amit KapilaDiscussion:https://postgr.es/m/OS0PR01MB5716AF9079CC0755CD015322947E9@OS0PR01MB5716.jpnprd01.prod.outlook.com1 parentce6f8d9 commit0e0f6e2
1 file changed
+6
-0
lines changedLines changed: 6 additions & 0 deletions
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
3562 | 3562 |
| |
3563 | 3563 |
| |
3564 | 3564 |
| |
| 3565 | + | |
| 3566 | + | |
| 3567 | + | |
| 3568 | + | |
| 3569 | + | |
| 3570 | + | |
3565 | 3571 |
| |
3566 | 3572 |
| |
3567 | 3573 |
| |
|
0 commit comments
Comments
(0)