LALapalux·Aug 1, 2026
Integresql has been a very helpful tool for us - we spin up many temporary postgres dbs during e2e testing
https://github.com/allaboutapps/integresql
In Pgtestdb's template cloning approach to testing is fastallaboutapps
integresql
Go2020–2026
allaboutapps / integresql
integresql
IntegreSQL manages isolated PostgreSQL databases for your integration tests.
7Distinct people
12Mentions
0Explicit recommenders
810GitHub stars
What to know before exploring
What it is
IntegreSQL manages isolated PostgreSQL databases for your integration tests.
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year12 dated mentions
Observed mentions: 2020-07-09 20:49:09 UTC to 2026-08-01 20:49:50 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 1 | 0 | 1 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
12 sourcesUff, I had no idea that Postgres v15 introduced WAL_LOG and changed the defaults from FILE_COPY. For (parallel CI) test envs, it make so much sense to switch back to the FILE_COPY strategy ... and I previously actually relied on that behavior.
Raised an issue in my previous pet project for doing concurrent integration tests with real PostgreSQL DBs (https://github.com/allaboutapps/integresql) as well.
In Instant database clones with PostgreSQL 18I'm bothering the PGLite team a lot to help us enable this :-)
We have different options like embedded-postgres or integreSQL, but none match the simplicity of PGLite. I hope this wish comes true soon.
https://github.com/fergusstrange/embedded-postgres/tree/mast...
https://github.com/allaboutapps/integresql
In Show HN: PGlite – in-browser WASM Postgres with pgvector and live syncHappy to hear that! When it comes to testing services that depend on PostgreSQL, this is still my preferred solution.
https://github.com/allaboutapps/integresql
disclaimer: author
In Ask HN: How do you test SQL?Not so crazy, it's very feasible to roll it yourself! Postgres has a "copy database" feature that's very useful (`CREATE DATABASE xxx WITH TEMPLATE yyy`).
I saw a project on HN a while ago focused on "managing isolated PostgreSQL databases for your integration tests", never used it but looks like a good idea: https://github.com/allaboutapps/integresql
In We killed our end-to-end test suiteIntegreSQL – isolated PostgreSQL databases for integration tests
1 points · Open discussionI haven't had a chance to try it yet, but IntegreSQL[0] looks like this on steroids. It allows you to create a template (run migrations and seed data), and then uses Postgres's built in cloning functionality to maintain a pool of fresh databases. They claim 500ms to clone a database without the pool, and that the pool pretty much hides the latency entirely.
[0]: https://github.com/allaboutapps/integresql
In Pg_tmp – Run tests on an isolated, temporary PostgreSQL databaseWhile PostgreSQL templates allow to scaffold new databases (one per test-spec) quite fast, it's even faster to have a warmed up pool of databases ready: https://github.com/allaboutapps/integresql#background
Disclaimer: author.
In DuckDB – An embeddable SQL database like SQLite, but supports Postgres featuresGreat points! Any hints regarding preexisting linters for go code that errors if we execute outside (an already opened) db transaction?
Also, regarding writing tests against real PostgreSQL databases, isolated per test and without losing speed, I can recommend to take a look at https://github.com/allaboutapps/integresql - disclaimer, we are the authors.
In Testing Database Transactions in GoI'm sorry, our documentation is not ready for primetime yet (an OpenAPI spec for this RESTful JSON API managing PostgreSQL test databases is still missing).
However, I've just updated the Background - feel free to file an issue if some aspect is totally left in the dark.
https://github.com/allaboutapps/integresql#background
In IntegreSQL – PostgreSQL optimised for integration testingIntegreSQL – PostgreSQL optimised for integration testing
1 points · Open discussionWe are using PostgreSQL templates to speed up our integration tests. This allow us to have full blown (and non mocked) databases which are isolated to each parallel running test.
We have recently open-sourced our core-server managing this (go): https://github.com/allaboutapps/integresql
Projects already utilizing Go and PostgreSQL may easily adapt this concept for their testing via https://github.com/allaboutapps/integresql-client-go
In PostgreSQL Templates