porsager / porsager/postgres

Current number of connections in use

Open
#443 14 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
JavaScript
Stars
8.7k
Forks
374
Avg merge
11d 16h
Merged PRs (30d)
1

Description

We used to use pg and pg-pool which would expose the number of connections in use and the number available.

Our use case is that this would let us have a health endpoint that our load balancer could use to determine if the server is overloaded query-wise (cpu and request could could still be low but connections could be maxed out and queries taking too long for some reason).

Is there any way to do this?

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No file or test is named in the issue. Start by tracing how the client manages pooled PostgreSQL connections and whether it records in-use and available counts; done would be a documented, tested way to obtain those counts for a health endpoint.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, node.js, postgresql
Domain
databases
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.