You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sqldb: add global lock config options for postgres
Add two configuration options to control global lock usage for
different postgres database backends:
- ChannelDBWithGlobalLock: for channeldb access (default: false)
- WalletDBWithGlobalLock: for wallet database access (default: true)
These allow fine-grained control over which databases use global
locks, rather than hardcoding the behavior. This is a temporary
measure until the revocation log and wallet are migrated to native
SQL and become fully concurrent-safe.
Timeout time.Duration`long:"timeout" description:"Database connection timeout. Set to zero to disable."`
49
+
MaxConnectionsint`long:"maxconnections" description:"The maximum number of open connections to the database. Set to zero for unlimited."`
50
+
SkipMigrationsbool`long:"skipmigrations" description:"Skip applying migrations on startup."`
51
+
ChannelDBWithGlobalLockbool`long:"channeldb-with-global-lock" description:"Use a global lock for channeldb access. This ensures only a single writer at a time but reduces concurrency. This is a temporary workaround until the revocation log is migrated to a native sql schema."`
52
+
WalletDBWithGlobalLockbool`long:"walletdb-with-global-lock" description:"Use a global lock for wallet database access. This ensures only a single writer at a time but reduces concurrency. This is a temporary workaround until the wallet subsystem is upgraded to a native sql schema."`
53
+
QueryConfig`group:"query" namespace:"query"`
52
54
}
53
55
54
56
// Validate checks that the PostgresConfig values are valid.
0 commit comments