Jelte Fennema-Nio

@dmitry-lipetsk are you still planning to move this forward? On a related note, there's now a discord channel to discuss PgBouncer development, feel free to join there: https://discordapp.com/channels/1258108670710124574/1300532992304742481

I wanted to remap `q` from Quit to Return for non prompt options (this is hard-wired in my brain from `tig`). But with the current available keybindings that's not possible,...

First of all, I'm a bit confused. Your PR description seems to be about a completely different feature than the actual feature that's implemented in the code. Secondly regarding this...

I think this goal of this PR makes a lot of sense, but I think this needs a review from someone that's more experienced in C++ than me. @Y-- what...

Moved this to 0.2.0, in that release we'll do a more holistic approach to solving these issues.

@Y-- Does this still make sense? Or should we close this one? It seems like you haven't needed this for your cleanup so far?

A user of pg_duckdb hit this problem. They couldn't see the HINT that was provided by the extension in the error: https://github.com/duckdb/pg_duckdb/issues/696#issuecomment-2812381593

I'm pretty sure you should be able to use `#[from(forward)]` to achieve this.

The error you're getting indicates that tokio_postgres is asking to execute a prepared statement name which PgBouncer doesn't recognize. > * A new connection is created for every query (for...

If what I wrote is indeed the cause, this is arguably a bug in tokio_postgres. Because it shouldn't allow running a prepared statement from client X on client Y.