How We Went All In on sqlc/pgx for Postgres and Go

Re:How We Went All In on sqlc/pgx for Postgres and Go by jvolkman on Thursday September 09, 2021 @10:26AM (#28470034)

What does your bazel tooling look like? We use postgres and bazel together in automated tests and I'm curious about how others start and manage postgres instances in similar scenarios. Currently were driving postgres from Python (py.test) while running tests.

The issue with our current approach is that we need to keep the bazel tests fairly coarse (e.g., one bazel test for dozens of python tests) to keep the overhead of starting postgres instances down.

[ Parent | on HN ]

Re:How We Went All In on sqlc/pgx for Postgres and Go by sa46 on Thursday September 09, 2021 @01:13PM (#28472062)

I uploaded most of our Workspace setup here: https://github.com/jschaf/bazel-postgres-sketch. The tooling is a bunch of Go to manage the Postgres process. Basically, give it schema files and receive a running database with a tear down command.

We make temp instances of Postgres quickly by:

- avoiding Docker, especially on Mac

- keeping the data dir on tmpfs

- Disable initdb cleanup

- Disable fsync and other data integrity flags

- Use unlogged tables.

- Use sockets instead of TCP localhost.

For a test suite, it was 12x faster to call createdb with the same Postgres cluster for each test than than to create a whole new db cluster. The trick was to create a template database after loading the schema and use that for each createdb call.

[ Parent | on HN ]

Re:How We Went All In on sqlc/pgx for Postgres and Go by jvolkman on Thursday September 09, 2021 @01:32PM (#28472297)

Cool, thanks for the link.

For what it's worth, we use rules_nixpkgs to source Postgres (for Linux and Darwin) as well as things such as C and Python toolchains, and it's been working really well. It does require that the machine have Nix installed, though, but that opens up access to Nix's wide array of prebuilt packages.

https://github.com/tweag/rules_nixpkgs

[ Parent | on HN ]