| From: | Vaibhav Rastogi <Vaibhav(dot)Rastogi(at)sas(dot)com> |
|---|---|
| To: | "pgpool-general(at)lists(dot)postgresql(dot)org" <pgpool-general(at)lists(dot)postgresql(dot)org> |
| Cc: | Rajesh Kazhankodath <Rajesh(dot)Kazhankodath(at)sas(dot)com>, Rahul Sarda <Rahul(dot)Sarda(at)sas(dot)com>, Sahil Kulkarni <Sahil(dot)Kulkarni(at)sas(dot)com>, Rajan Pawar <Rajan(dot)Pawar(dot)External(at)sas(dot)com> |
| Subject: | pgpool-II 4.4.16: Version mismatch between configure.ac and generated configure script |
| Date: | 2026-04-02 09:44:18 |
| Message-ID: | IA1PR05MB1127532A35D49B633324F7FC0EC51A@IA1PR05MB11275.namprd05.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgpool-general |
Hello pgpool-II team,
We are currently evaluating pgpool-II 4.4.16 and noticed a possible version inconsistency in the release artifacts.
In the 4.4.16 tag/branch:
* configure.ac has been updated to version 4.4.16
* However, the generated configure script still reports version 4.4.15
In our setup, pgpool-II is used as a git submodule. After building and installing pgpool-II from this source, running the installed binary reports the version as 4.4.15, even though we are building from the 4.4.16 sources.
This suggests that the configure script may not have been regenerated after updating configure.ac.
Could you please confirm:
* Whether this is a known issue in the 4.4.16 release, and
* If the configure script is expected to be regenerated (for example via autoreconf) before release?
We wanted to report this in case it affects others building from source or using pgpool-II as a submodule.
Thank you for your time and for maintaining pgpool-II.
Best regards,
Vaibhav Rastogi
Sr Software Developer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | JOSE MARIA Marin | 2026-04-06 11:14:36 | Bug report: Hardcoded debug logs "pi->node_ids" in pcp_child (v4.7.0) |
| Previous Message | zam bak | 2026-03-05 18:25:58 | Fwd: RPM packages for "aarch64" platform |