void-linux / void-linux/void-packages
PostgreSQL 16 initdb fails with dict_snowball.so: undefined symbol: CurrentMemoryContext
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 3.4k
- Forks
- 2.8k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 299
Description
Is this a new report?
Yes
System Info
Void 5.10.160 aarch64 Unknown uptodate rrnFFFF
Package(s) Affected
postgresql16-16.2_1
Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://lore.kernel.org/buildroot/20240117210756.265708-1-ju.o@free.fr/
Expected behaviour
PostgreSQL 16 initdb succeeds
Actual behaviour
When the postgresql16 service is started without existing data, initdb is run and yields:
FATAL: could not load library "/usr/lib/psql16/lib/postgresql/dict_snowball.so": /usr/lib/psql16/lib/postgresql/dict_snowball.so: undefined symbol: CurrentMemoryContext
It then remains stuck in a loop trying to run initdb and failing.
This appears to affect aarch64 but not x86_64.
Steps to reproduce
Install fresh copy of PostgreSQL 16 (on aarch64)
Start the postgresql16 service or run initdb manually
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the PostgreSQL 16 initdb failure on aarch64 and compare it with the linked upstream report. Inspect the PostgreSQL 16 package and service entry point, then verify that a fresh postgresql16 service starts without the dict_snowball.so undefined-symbol error or an initdb retry loop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100