Release / Upgrade pg-pool package

[moritzuehling]

Hi there!

I just ran into #3508 which was fixed in #3509. Based on the commit, this was merged on July 10th, a couple weeks after the last release (3.10.1) of pg-pool (June 18th, according to NPM)

Current main does seem to include API changes unfortunately, so I'm not sure what the best strategy is, and if this package follows semver.

The above commit is the only other change I can see (to pg-pool), though, so there's potential to release a version 3.10.2 that just cherry-picks 01fadd9.

Is there a timeline to release a version of pg-pool with the fix? For now, we'll hopefully just not run into this, and maybe set the min a bit higher to reduce the chances of a cold-start with slightly bursty load, but it would be cool to have a fix.

Thanks!

-- Moritz

[charmander]

All the pg packages follow semver. The changes in the main branch should be backward-compatible. (Of course, mistakes happen sometimes.)

[moritzuehling]

In that case, a release would be much appreciated, as that bug does affect us somewhat. I'd prefer if we can keep some connections open, even if there's somewhat bursty workloads.

Thanks a lot, again :)

[6uliver]

I just ran into same problem. When could you release the bugfix to npm?