PostgreSQL Extensions in Go

valyala 133 points 23 comments November 21, 2026
jespino.github.io · View on Hacker News

Discussion Highlights (8 comments)

3eb7988a1663

The Go community sold me on the necessity of programming mascots. The gopher is adorable, and I love seeing the creative tweaks for how people incorporate it into their marketing. Ferris the crab also seems like it has been around since the early days, but I do not see nearly as many projects with crab heavy media. Guess it also has to be a mammal.

angrydingo

for code snippets on darkmode i can't see bracket

Wicher

See also https://gitlab.com/microo8/plgo

ltbarcly3

LLMs make "I need to shoehorn a language I already know well into an environment where it doesn't really belong" an unnecessary extravagance. Just have an AI write plpgsql. If what you are doing is too complicated for plpgsql you are doing something stupid.

QGQBGdeZREunxLe

From the same author: https://jespino.github.io/gokm/ (Linux kernel modules in Go)

Icathian

Okay now this is cool. Anything to make postgres extensions nice and easy to write. Still gonna go with pgrx though.

Kinrany

Now that reimplementing old ideas is a commodity, can't we have a new database without carrying the historical baggage and bad decisions of old?

philippemnoel

More people using and extending Postgres is a huge win for the ecosystem, but I am somewhat uncertain of the appeal of Go for this task. It seems to really shine at "platform"-level tasks (e.g. K8s, network proxies, etc. etc.), while Postgres extensions are more at the data plane level.

Semantic search powered by Rivestack pgvector
13,334 stories · 126,150 chunks indexed