Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Name the pool settings dbkit/postgres refuses by an app's own setting

Open
  • Is something wrong?
#91 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
Half a day
Newbie friendliness
55/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go, postgresql
Domain
database

Research direction

Start in the dbkit/postgres package at Open, where pool_max_conns, pool_min_conns and pool_min_idle_conns are refused with a message that names Options.MaxConns. Find where the pool settings are read from the address and add a check for pool_max_conn_idle_time, one of the eight pgx 5.11 pool settings. Done when an address with each refused key returns an error naming the key the app's user sees, that error is exported, and idle time is validated.

Written by the indexing model from the issue text.

Description

enhancement help wanted

What

  • dbkit/postgres Open refuses pool_max_conns, pool_min_conns and pool_min_idle_conns with a message that names Options.MaxConns, a Go option the person editing the address never sees. Export the error, or the key it found, so an app can name its own setting instead.
  • Open does not check pool_max_conn_idle_time, one of the eight pool settings pgx 5.11 reads from an address.

Why

An app that sizes the pool from its own setting cannot point people to that setting today, and one pool setting slips past the checks.

Dominant language
Go
Stars
69
Forks
3
Avg merge
9h 11m
Merged PRs (30d)
38

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from gopherium/framework

All issues in gopherium/framework

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.