Feature compatibility

Server feature/commit scope interoperability

Not all server features work with all commit scopes. This table shows the ones that interoperate.

	Async<br />(default)	Parallel Apply	Using with transaction streaming	Decoding worker
Group Commit (legacy)	N/A	Does not combine	Does not interoperate <sup>❗️</sup>	Combines
Commit At Most Once	N/A	Combines	Does not interoperate	Does not interoperate
Lag Control	Combines	Combines	Combines	Combines
Synchronous Commit	N/A	Combines	Combines	Combines

Notes

N/A : 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 (legacy)	Commit At Most Once	Lag Control	Synchronous Commit
Group Commit (legacy)	N/A	Does not combine	Combines	Combines
Commit At Most Once	Does not combine	N/A	Combines	Does not combine
Lag Control	Combines	Combines	N/A	Combines
Synchronous Commit	Combines	Does not combine	Combines	N/A

Notes

Each commit scope implicitly works with itself.