hasql-resource-pool: A pool of connections for Hasql based on resource-pool.

[ database, hasql, library, mit, postgresql ] [ Propose Tags ]

This package is originally derived from hasql-pool v0.5.2.2 and continues using `resource-pool` for its pool implementation.


[Skip to Readme]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

Versions [RSS] 0.5.3.0, 0.5.3.1, 0.5.3.2, 0.5.4.0, 0.5.4.1, 0.6.0.0 (info)
Change log CHANGELOG.md
Dependencies base-prelude (>=1 && <2), clock (>=0.8), hasql (>=1.6.3), resource-pool (>=0.4.0.0), time (>=1.5 && <2) [details]
License MIT
Copyright (c) 2023, Maxim Avanov
Author Nikita Volkov <nikita.y.volkov@mail.ru>
Maintainer Maxim Avanov <maxim.avanov@gmail.com>
Category Hasql, Database, PostgreSQL
Home page https://github.com/avanov/hasql-resource-pool
Bug tracker https://github.com/avanov/hasql-resource-pool/issues
Source repo head: git clone git://github.com/avanov/hasql-resource-pool.git
Uploaded by avanov at 2023-03-08T02:46:29Z
Distributions
Downloads 293 total (20 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2023-03-08 [all 1 reports]

Readme for hasql-resource-pool-0.6.0.0

[back to package description]

hasql-resource-pool

This is a fork of hasql-pool that continues using resource-pool for its underlying pool implementation.

The fork is based on 0.5.2.2 release (as the latest original implementation based on resource-pool), and it includes the following API and layout changes:

  • Connections are based on settings with IO actions. This change to the API makes the library usable with the custom authentication methods such as AWS RDS IAM tokens.
  • Pool interface allows for specifying IO observer actions. These actions are useful for collecting and tracking various pool metrics with tools like Prometheus.
  • Decision making on the size of the stripes is delegated to the upgraded resource-pool (which has slightly different semantics compared to v0.2.x).
  • No reliance on Stack tooling.