Lev Kokotov
Lev Kokotov
You actually want to implement `std::fmt::Display` which will give you both a `ToString` and `display()` implementation we can use for `prinlnt!`, `log!`, etc.
I think this is because `bb8` asynchronously spawns new connections when multiple clients request one and the pool doesn't have any idle ones available: https://github.com/djc/bb8/blob/main/bb8/src/inner.rs#L102-L147. I believe Pgb is doing...
Thank you for this. I'll review it asap.
Hi. Thank you for the PR. I haven't forgotten about it, I'll try to review it sometime this weekend or early next week. Please feel free to ping me again...
Why don't we just demote the warn to an info or debug? We don't need this additional machinery to hide a warning I don't think unless I'm missing some foundational...
> the issue is still there that we will end up trying to parse an unsupported query I suspect the list of unsupported queries is not exhaustive and we'll end...
Now that I'm thinking more about this, I would rather we log a warning than nothing at all. This is an error condition that we're currently not handling well, so...
Isn't this expected? Why should we be able to return large result sets at the same speed as small ones?
https://github.com/postgresml/pgcat/issues/616#issuecomment-1850518179
We don't use Kubernetes anymore, but I'm happy to accept a PR with a Helm chart.