comparison PostgreSQL/NEWS @ 432:8b7c1c423367 pg-transactions

new 'TransactionMode' config + rewrote ResourceDeletedFunc to avoid IF/THEN/ELSE pattern
author Alain Mazy <am@osimis.io>
date Mon, 11 Dec 2023 14:39:27 +0100
parents f1f3c5554283
children ff84104f7842
comparison
equal deleted inserted replaced
431:7c1fe5d6c12c 432:8b7c1c423367
1 Pending changes in the mainline 1 Pending changes in the mainline
2 =============================== 2 ===============================
3 3
4 * Experimental debug feature: 4 * Experimental debug feature:
5 Introduced 2 new configurations with these default values: 5 Introduced a new configuration to select the transaction isolation level
6 "ReadOnlyTransactionStatement": "SET TRANSACTION ISOLATION LEVEL SERIALIZABLE READ ONLY" 6 "TransactionMode": "SERIALIZABLE"
7 "ReadWriteTransactionStatement": "SET TRANSACTION ISOLATION LEVEL SERIALIZABLE READ WRITE" 7 Allowed values: "SERIALIZABLE", "READ COMMITTED", "DEFAULT".
8 You can now customize the transaction isolation level. 8 The "SERIALIZABLE" mode was the only available value up to now. It is still the default
9 If setting these values to "", no statement is run and therefore, the default DB or server 9 value now.
10 isolation level is used. 10 The "READ COMMITTED" is possible now due to rewrites of SQL queries.
11 The "DEFAULT" value uses the default transaction isolation level defined at the database level.
11 * internals: 12 * internals:
12 - Added a UNIQUE constraint on Resources.publicId to detect DB inconsistencies 13 - Added a UNIQUE constraint on Resources.publicId to detect DB inconsistencies
13 * New "EnableVerboseLogs" configuration to show SQL statements being executed. 14 * New "EnableVerboseLogs" configuration to show SQL statements being executed.
14 15
15 16