PostgreSQL 18.3, 17.9, 16.13, 15.17, and 14.22

[jwaisner]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Add PostgreSQL 18.3, 17.9, 16.13, 15.17, and 14.22 support

✨ Enhancement

Walkthroughs

Description

• Add support for PostgreSQL versions 18.3, 17.9, 16.13, 15.17, and 14.22
• Create configuration files for each new PostgreSQL version
• Update release properties with download URLs for new versions
• Update bundle release version to 2025.3.8

Diagram

flowchart LR
  A["New PostgreSQL Versions"] --> B["Configuration Files"]
  A --> C["Release Properties"]
  B --> D["bearsampp.conf"]
  B --> E["postgresql.conf.ber"]
  B --> F["pg_hba.conf.ber"]
  B --> G["init.bat"]
  C --> H["Version URLs"]
  H --> I["Bundle Release 2025.3.8"]

Loading

File Changes

1. releases.properties ⚙️ Configuration changes +5/-0

Add new PostgreSQL version download URLs

releases.properties

---

2. gradle.properties ⚙️ Configuration changes +1/-1

Update bundle release version number

gradle.properties

---

3. bin/postgresql18.3/init.bat ⚙️ Configuration changes +5/-0

Add initialization script for PostgreSQL 18.3

bin/postgresql18.3/init.bat

---

View more (20)

4. bin/postgresql18.3/bearsampp.conf ⚙️ Configuration changes +14/-0

Add Bearsampp configuration for PostgreSQL 18.3

bin/postgresql18.3/bearsampp.conf

---

5. bin/postgresql18.3/postgresql.conf.ber ⚙️ Configuration changes +35/-0

Add PostgreSQL configuration template for 18.3

bin/postgresql18.3/postgresql.conf.ber

---

6. bin/postgresql18.3/pg_hba.conf.ber ⚙️ Configuration changes +3/-0

Add host-based authentication config for 18.3

bin/postgresql18.3/pg_hba.conf.ber

---

7. bin/postgresql17.9/init.bat ⚙️ Configuration changes +5/-0

Add initialization script for PostgreSQL 17.9

bin/postgresql17.9/init.bat

---

8. bin/postgresql17.9/bearsampp.conf ⚙️ Configuration changes +14/-0

Add Bearsampp configuration for PostgreSQL 17.9

bin/postgresql17.9/bearsampp.conf

---

9. bin/postgresql17.9/postgresql.conf.ber ⚙️ Configuration changes +35/-0

Add PostgreSQL configuration template for 17.9

bin/postgresql17.9/postgresql.conf.ber

---

10. bin/postgresql17.9/pg_hba.conf.ber ⚙️ Configuration changes +3/-0

Add host-based authentication config for 17.9

bin/postgresql17.9/pg_hba.conf.ber

---

11. bin/postgresql16.13/init.bat ⚙️ Configuration changes +5/-0

Add initialization script for PostgreSQL 16.13

bin/postgresql16.13/init.bat

---

12. bin/postgresql16.13/bearsampp.conf ⚙️ Configuration changes +14/-0

Add Bearsampp configuration for PostgreSQL 16.13

bin/postgresql16.13/bearsampp.conf

---

13. bin/postgresql16.13/postgresql.conf.ber ⚙️ Configuration changes +35/-0

Add PostgreSQL configuration template for 16.13

bin/postgresql16.13/postgresql.conf.ber

---

14. bin/postgresql16.13/pg_hba.conf.ber ⚙️ Configuration changes +3/-0

Add host-based authentication config for 16.13

bin/postgresql16.13/pg_hba.conf.ber

---

15. bin/postgresql15.17/init.bat ⚙️ Configuration changes +5/-0

Add initialization script for PostgreSQL 15.17

bin/postgresql15.17/init.bat

---

16. bin/postgresql15.17/bearsampp.conf ⚙️ Configuration changes +14/-0

Add Bearsampp configuration for PostgreSQL 15.17

bin/postgresql15.17/bearsampp.conf

---

17. bin/postgresql15.17/postgresql.conf.ber ⚙️ Configuration changes +35/-0

Add PostgreSQL configuration template for 15.17

bin/postgresql15.17/postgresql.conf.ber

---

18. bin/postgresql15.17/pg_hba.conf.ber ⚙️ Configuration changes +3/-0

Add host-based authentication config for 15.17

bin/postgresql15.17/pg_hba.conf.ber

---

19. bin/postgresql14.22/init.bat ⚙️ Configuration changes +5/-0

Add initialization script for PostgreSQL 14.22

bin/postgresql14.22/init.bat

---

20. bin/postgresql14.22/bearsampp.conf ⚙️ Configuration changes +14/-0

Add Bearsampp configuration for PostgreSQL 14.22

bin/postgresql14.22/bearsampp.conf

---

21. bin/postgresql14.22/pg_hba.conf.ber Additional files +3/-0

...

bin/postgresql14.22/pg_hba.conf.ber

---

22. bin/postgresql14.22/postgresql.conf.ber Additional files +35/-0

...

bin/postgresql14.22/postgresql.conf.ber

---

23. build/reports/problems/problems-report.html Additional files +0/-659

...

build/reports/problems/problems-report.html

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (2) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. bundle.release regression risk 🐞 Bug ✓ Correctness

Description

bundle.release was changed from 2025.7.2 to 2025.3.8; this value is used by the Gradle build as the
project version and to name release archives, and it is embedded into the new releases.properties
URLs. If this is accidental (date regression), it can cause confusing/incorrect artifact naming and
mismatches between what CI/users expect vs what is published.

Code

gradle.properties[5]

+bundle.release = 2025.3.8

Evidence

gradle.properties defines bundle.release=2025.3.8, and build.gradle uses bundle.release as both the
Gradle project version and as part of the archive filename. releases.properties new entries embed
2025.3.8 in the artifact filenames, while older entries embed 2025.7.2, making the newest versions
appear built for an older bundle release unless this was intentionally changed.

gradle.properties[4-7]
build.gradle[27-41]
build.gradle[587-589]
releases.properties[1-5]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`bundle.release` was changed to an older-looking value (`2025.3.8` vs previously `2025.7.2`). This value is used in archive naming, build output paths, and is embedded in `releases.properties` URLs for the newly added versions. If the change is accidental, it will cause inconsistent/incorrect artifact naming and confusion for consumers.

## Issue Context
- `bundle.release` is consumed by Gradle as the project `version` and included in the produced archive name.
- New `releases.properties` entries embed the same bundle.release in the artifact filename.
- Verify whether this PR is meant to publish artifacts for an older Bearsampp bundle release, or whether this is a date/version typo.

## Fix Focus Areas
- gradle.properties[4-7]
- releases.properties[1-5]
- build.gradle[27-41]
- build.gradle[587-589]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

2. Insecure default Postgres templates 🐞 Bug ⛨ Security

Description

The newly added version bundles ship templates that initialize PostgreSQL with trust authentication,
set an empty root password, listen on all interfaces, and use world-writable log permissions. Even
with loopback-only pg_hba entries, these defaults enable passwordless local access and reduce
defense-in-depth if pg_hba is later loosened or misapplied.

Code

bin/postgresql18.3/init.bat[3]

+%~dp0bin\initdb.exe -U postgres -A trust -E utf8 -D "%~dp0data" > "~BEARSAMPP_WIN_PATH~\logs\postgresql-install.log" 2>&1

Evidence

The added templates use initdb -A trust, configure pg_hba to trust localhost, set
listen_addresses='*', and leave the configured root password empty. Documentation notes trust is
used for testing, but these files are shipped as bundle defaults, not just CI test scaffolding.

bin/postgresql18.3/init.bat[1-5]
bin/postgresql18.3/pg_hba.conf.ber[1-3]
bin/postgresql18.3/postgresql.conf.ber[9-13]
bin/postgresql18.3/postgresql.conf.ber[23-30]
bin/postgresql18.3/bearsampp.conf[10-12]
docs/CI-CD-TESTING.md[115-122]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The newly added PostgreSQL bundle templates ship insecure defaults (trust auth, empty password, listen on all interfaces, world-writable logs). These defaults are risky outside a strictly local dev sandbox and reduce defense-in-depth.

## Issue Context
These templates are part of the version bundles under `bin/postgresqlX.Y/` and will be used by end-users, not just CI.

## Fix Focus Areas
- bin/postgresql18.3/init.bat[1-5]
- bin/postgresql18.3/pg_hba.conf.ber[1-3]
- bin/postgresql18.3/postgresql.conf.ber[9-13]
- bin/postgresql18.3/postgresql.conf.ber[23-30]
- bin/postgresql18.3/bearsampp.conf[10-12]
- bin/postgresql17.9/init.bat[1-5]
- bin/postgresql17.9/pg_hba.conf.ber[1-3]
- bin/postgresql17.9/postgresql.conf.ber[9-13]
- bin/postgresql17.9/postgresql.conf.ber[23-30]
- bin/postgresql17.9/bearsampp.conf[10-12]
- bin/postgresql16.13/init.bat[1-5]
- bin/postgresql16.13/pg_hba.conf.ber[1-3]
- bin/postgresql16.13/postgresql.conf.ber[9-13]
- bin/postgresql16.13/postgresql.conf.ber[23-30]
- bin/postgresql16.13/bearsampp.conf[10-12]
- bin/postgresql15.17/init.bat[1-5]
- bin/postgresql15.17/pg_hba.conf.ber[1-3]
- bin/postgresql15.17/postgresql.conf.ber[9-13]
- bin/postgresql15.17/postgresql.conf.ber[23-30]
- bin/postgresql15.17/bearsampp.conf[10-12]
- bin/postgresql14.22/init.bat[1-5]
- bin/postgresql14.22/pg_hba.conf.ber[1-3]
- bin/postgresql14.22/postgresql.conf.ber[9-13]
- bin/postgresql14.22/postgresql.conf.ber[23-30]
- bin/postgresql14.22/bearsampp.conf[10-12]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more

[github-actions]

🐘 PostgreSQL Module Tests - Results

Test Date: 2026-03-08 06:23:18 UTC
Status: ✅ All tests passed

📊 Test Results by Version

Results: 5 of 5 versions tested

All tests passed successfully! ✨

---

📋 Test Phases

Each version is tested through the following phases:

• Phase 1: Installation Validation (Download, Extract, Verify Executables)
• Phase 2: Basic Functionality (Test Executable Versions)

Check artifacts for detailed logs.