Kostya Vasilyev

> Is it also planed to package the cluster version? As far as I can tell, the cluster version is a separate branch (as opposed to a build target within...

Created a draft PR: https://github.com/VictoriaMetrics/VictoriaMetrics/pull/116

Same here on Ubuntu 22.04, and the fix in #97 helped. Maybe it's also time to update the #! to python3 :)

@dattas I'm the developer of AquaMail. There is no such thing as "the" notification -- in my app, people usually use one notification per account (so they'd have to be...

More info: The query that fails for me, and it was the first query executed on a particular code path, is an UPSERT like this: ``` _, err := model.db.Exec(context.Background(),...

I did some debugging, adding trace printouts to `PgConn.lock` and `PgConn.unlock`. I believe there is a bug in `Conn.QueryRow` - it calls `Query` behind the scenes which locks the connection...

One more thing re: my earlier comment on Query continuing to work even when Upsert starting throwing "conn busy". As it turns out, Query is missing error propagation when pgConn.lock()...

A simple reproducer: ``` wg := sync.WaitGroup{} wg.Add(10) for coIter := 0; coIter < 10; coIter += 1 { go func() { for nowIter := 0; nowIter < 100; nowIter...

Thank you @durango I'll be looking forward to it getting merged. In the meantime I'm wondering if I should switch from pgx connection to pgx pool. My simple test passes...

About pgxpool. It also fails on concurrent workloads. ``` pgsqlConfig, err := pgxpool.ParseConfig("postgres://user:pass@localhost:5432/database") if err != nil { fmt.Println(err) return } pgxPool, err := pgxpool.ConnectConfig(context.Background(), pgsqlConfig) if err != nil...