←back to thread

What if we treated Postgres like SQLite?

(www.maragu.dev)
75 points markusw | 1 comments | 22 Sep 25 13:29 UTC | HN request time: 0s | source
Show context
nu11ptr ◴[22 Sep 25 15:55 UTC] No.45335239[source]▶
You can, just embed it in your Go app:

https://github.com/fergusstrange/embedded-postgres

replies(2): >>45335287 #>>45335384 #
OutOfHere ◴[22 Sep 25 16:04 UTC] No.45335384[source]▶
Does this use an external binary or CGO or Wazero (Wasm) or is it rewritten in Go?

With SQLite, although all approaches are available, my fav is to use https://github.com/ncruces/go-sqlite3 which uses Wazero.

I try to avoid CGO if I can because it adds compile-time complexity, making it unfriendly for a user to compile.

replies(1): >>45335515 #
1. nu11ptr ◴[22 Sep 25 16:13 UTC] No.45335515[source]▶
> Does this use an external binary or CGO or Wazero (Wasm) or is it rewritten in Go?

Since Postgres is always a network connection, I don't believe any CGo is required.

> I try to avoid CGO if I can because it adds compile-time complexity, making it unfriendly for a user to compile.

Using zig as your C compiler mostly fixes this, but you can't 100% get rid of the complexity, but I've cross compiled using Zig cc to Windows/Mac/Linux pretty easily via CGo.