vcswatch reports that
this package seems to have new commits in its VCS but has
not yet updated debian/changelog. You should consider updating
the Debian changelog and uploading this new version into the archive.
Here are the relevant commit logs:
commit 3716b68a3f8bd21e9ea1eb693b78f05acc226e29
Author: Antonin Houska <ah@cybertec.at>
Date: Tue Sep 26 15:35:19 2023 +0200
Remove old origin cleanup code.
This should have be done in the commit 89b85f2276.
commit cf793f2a3acb00f89362007335e6a310cc38fe2a
Author: Antonin Houska <ah@cybertec.at>
Date: Mon Sep 25 17:15:05 2023 +0200
Always pass only a single task to the squeeze worker.
So far, the squeeze_table() function assigned the task via shared memory
whereas the scheduled tasks were fetched by the squeeze worker itself. This
was messy, so refactored.
commit 39d917b8ab2dc1b1b75bccc5a80f38e709656fc1
Author: Antonin Houska <ah@cybertec.at>
Date: Mon Sep 25 16:58:29 2023 +0200
Fixed transaction handling in manage_session_origin().
This was omitted in the commit 89b85f2276.
commit 3e5d86fc7913d63155abb3526be77861103745ca
Author: Antonin Houska <ah@cybertec.at>
Date: Fri Sep 22 07:29:46 2023 +0200
Fixed filter in the query that checks the number of pending tasks.
commit 89b85f22767880575cb54d8c0526d29cf880219a
Author: Antonin Houska <ah@cybertec.at>
Date: Fri Sep 22 07:25:14 2023 +0200
Create and drop the replication origin in a separate transaction.
Due to the unique OID, one backend has to wait until another backend's
transaction, which also creates the origin commits. If the transaction
involves the actual squeeze work, the work done by multiple workers is
effectively serialized.
commit 63f1279d68cd427f62aec172e8f55a4aebda6d7a
Merge: 6a61c9d 9c63bac
Author: Antonin Houska <ah@cybertec.at>
Date: Tue Sep 19 17:45:54 2023 +0200
Merge remote-tracking branch 'origin/master'
commit 6a61c9d3379b400cd52f49715a54da85a8e506c9
Author: Antonin Houska <ah@cybertec.at>
Date: Tue Sep 19 15:42:54 2023 +0200
Only start the squeeze worker if there is some work to do.
Instead of letting one or more squeeze workers per database run all the time,
it seems better to let the scheduler worker start them only if there are
tables to squeeze. This design also simplifies the squeeze_table() function:
it's simpler to start a new worker and wait until it exits than to communicate
with an existing worker via shared memory.
![[bug history graph]](https://qa.debian.org/data/bts/graphs/p/pg-squeeze.png){kind=link}