Error listening on topic "river_leadership"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.7k
- Forks
- 179
- Avg merge
- 15h 43m
- Merged PRs (30d)
- 13
Description
I am using aws rds, postgres v17.
I get this issue randomnly and this gets fixed when i reboot the database, no other fixes works. Tried vacuum analyze, tried checking for the transaction it is stuck with, nothing worked. Please help
{"level":"fatal","file":"main.go","line":118,"error":"Failed to start River client: error listening on topic \"river_leadership\": ERROR: could not access status of transaction 830749165 (SQLSTATE 58P01)","time":"2025-07-03T07:50:44Z","message":"Failed to start River client: error listening on topic \"river_leadership\": ERROR: could not access status of transaction 830749165 (SQLSTATE 58P01)"}
Contributor guide
No contributing guide indexed for this repository
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 at main.go:118, where the River client startup failure is reported, and trace the listener for the river_leadership topic. Reproduce or investigate the transaction-status error with AWS RDS PostgreSQL 17, using the reported SQLSTATE 58P01 and transaction ID as clues. Done means identifying a repository-side cause and documenting or testing a fix; the issue does not name an existing test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, postgresql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100