Async PG support #412
Async PG support #412
Conversation
| @@ -1141,9 +1166,14 @@ where | |||
|
|
|||
| // Sync | |||
| // Frontend (client) is asking for the query result now. | |||
There was a problem hiding this comment.
It would be nice to update these docs to include Flush. Something like:
// Sync (S)
// Frontend (client) is asking for the query result now.
// ... or ...
// Flush (H)
// Frontend (client) is asking for server to send query results now without
// sync.
|
This looks pretty good to me. Conflicts should be pretty easy to resolve. Is there something about this that you don't love that keeps this in a draft state? |
|
I don't think it actually works. I tested it locally, but it fails in CI. Haven't had time to investigate further yet. |
|
Hi, any update with this issue, I have similar problem when running this with python code. Thanks for update |
|
Would love a progress update on this one |
| ) | ||
| .await | ||
| { | ||
| let message = tokio::select! { |
There was a problem hiding this comment.
I tested this idea trying to see if this helps with #303
Something else it's missing that doesn't allow to send the server messages to the client. Maybe this 2 issues are related and could be solved both with the same fix
Fix #396