Feature compatibility v5
Server feature/commit scope interoperability
Not all server features work with all commit scopes. This table shows the ones that interoperate.
| Async (default) | Parallel Apply | Transaction Streaming | Single Decoding Worker | |
| Group Commit | ⛔︎ | ❌ | ❌❗️ | ✅ |
| CAMO | ⛔︎ | ✅ | ❌ | ❌ |
| Lag Control | ✅ | ✅ | ✅ | ✅ |
| Synchronous Commit | ⛔ ︎ | ✅ | ✅ | ✅ |
Legend: ⛔︎ Not applicable ❌ Does not interoperate ✅ Interoperates
Notes
⛔︎ : The Async column in the table represents PGD without a synchronous commit scope in use. Lag Control isn't a synchronous commit scope. It's a controlling commit scope and is therefore available with asynchronous operations.
❗️ : Attempting to use Group Commit and Transaction Streaming presents a warning. The warning suggests that you disable transaction streaming, and the transaction appears to take place. In the background, Group Commit was disabled to allow the transaction to occur.Commit scope/commit scope interoperability
Although you can't mix commit scopes, you can combine rules with an AND operator. This table shows where commit scopes can be combined.
| Group Commit | CAMO | Lag Control | Synchronous Commit | |
| Group Commit | ⛔︎ | ❌ | ✅ | ✅ |
| CAMO | ❌ | ⛔︎ | ✅ | ❌ |
| Lag Control | ✅ | ✅ | ⛔︎ | ✅ |
| Synchronous Commit | ✅ | ❌ | ✅ | ⛔︎ |
Legend: ⛔︎ Not applicable ❌ Does not combine ✅ Combines
Notes
Each commit scope implicitly works with itself.