I'm not sure whether it's in scope of x/perf/storage package to support environments other than what's needed for Go's own needs at perfdata.golang.org. There isn't an owner entry for this package, so I'm not sure if someone would have bandwidth to maintain it otherwise.

CC @prattmic.

I am slightly surprised to see someone running another production version of this. :) What is your use case? You simply want a custom/internal instance of perf.golang.org for your projects?

I am not particularly opposed to postgres support, but I also worry about maintenance; I suspect that it would break and we wouldn't even notice.

FWIW, we'll probably be changing these packages up a fair bit as part of #48803.

cc @aclements @mknyszek @dr2chase

The use case is to track benchmark data for projects that are not open sourced and where we don't want to expose the content of benchmark results. I was hoping to just start up a local instance of perf.golang.org.

It looks like the goal of #48803 is pretty much exactly what I'm trying to accomplish. Is that going to replace perf.golang.org or be an additional tool?

Current plan (we think) is that perf.golang.org will hold the benchmark data; for your purposes, sounds like we want to make that something that can be (re)configured w/o too much trouble.

Cleaning open tabs, noticed this, do you have a change-for-postgres already written, and available to look at? I do worry that we might break it, but if it's not large, maybe? I ask because I've messed with postgres in the past, had reason to use it recently in another context.

I have a change but I haven't had time to fully test or complete it. chriscasola@0fc0a1c

Oh dear. Thanks for that work, that makes me grumpy at the sql driver authors, some expect ?, ?, ? and others expect $1, $2, $3. Are you using pgx? I wonder if they would accept an "extension" along those lines.

It might be interesting to get rid of gratuitous incompatibilities, do the BIGINTs really need to be nonstandardly UNSIGNED?