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
{{ message }}
Repository navigation
Upgrade Postgres and start passing CancellationToken to PrepareAsync() if issue is resolved #111
changed the title [-]Upgrade Postgres and start passing CancellationToken to PrepareAsync() once issue is resolved[/-][+]Upgrade Postgres and start passing CancellationToken to PrepareAsync() if issue is resolved[/+]on Dec 13, 2021
Activity
[-]Upgrade Postgres and start passing CancellationToken to PrepareAsync() once issue is resolved[/-][+]Upgrade Postgres and start passing CancellationToken to PrepareAsync() if issue is resolved[/+]M4urici0GM commentedon Nov 5, 2023
Isnt this closed with postgre;'s #4559 ?
madelson commentedon Nov 5, 2023
@M4urici0GM seems like it is, so this issue can be addressed in the next release of the postgres DistributedLock lib.
Bartleby2718 commentedon Feb 25, 2024
@madelson Given the latest comment, I think we'll need a major version bump for
npgsql.The breaking changes introduced in npgsql major version 6 don't seem to affect this library, but will this affect consumers?
madelson commentedon Feb 25, 2024
@Bartleby2718 I agree; I think we'd go all the way to 8.x.
Close madelson#111: Upgrade npgsql (Postgres) to the very latest vers…