I raised that awhile ago, I was told that Hyperdrive doesn't need it and it's omitted to not confuse
I raised that awhile ago, I was told that Hyperdrive doesn't need it and it's omitted to not confuse users
prepare: false when making your connection in postgres.js, it'll be slower (less caching, can't take advantage of the prepared statement) but still correctly supported


tokio-postgres crate) using the query method. This uses the extended query protocol. I am observing the following behavior. When the Hyperdrive cache is:UnexpectedMessage error). I suspect disabled caching makes Hyperdrive use one connection for preparation and another execution on another. Occasionally, it might use the same connection, leading to a successful query.query would always fail regardless of the cache setting. So, I started working on a PR for the Postgres driver to make it work with Hyperdrive. But today, during testing that PR, I saw this behavior, thus this question.






query instead of simple_query.simple_query intentionally.prepare twice (as in https://github.com/sfackler/rust-postgres/blob/98f5a11bc0a8e451552d8941ffa078c7eb6cd60c/tokio-postgres/src/to_statement.rs#L18, which is invoked from https://github.com/sfackler/rust-postgres/blob/98f5a11bc0a8e451552d8941ffa078c7eb6cd60c/tokio-postgres/src/client.rs#L363.query will be better (to be measured, of course). If not, my fork avoids an extra roundtrip.prepare: falsetokio-postgresqueryqueryqueryqueryUnexpectedMessagesimple_querysimple_querylet res1 = client.query("SELECT * FROM FOO", &[]).await?;
let res2 = client.query("SELECT * FROM FOO", &[]).await?;prepare