mirror of
https://github.com/neondatabase/neon.git
synced 2025-12-22 21:59:59 +00:00
ed117af73e
In sqlstate, we have a manual `phf` construction, which is not explicitly guaranteed to be stable - you're intended to use a build.rs or the macro to make sure it's constructed correctly each time. This was inherited from tokio-postgres upstream, which has the same issue (https://github.com/rust-phf/rust-phf/pull/321#issuecomment-2724521193). We don't need this encoding of sqlstate, so I've switched it to simply parse 5 bytes (https://www.postgresql.org/docs/current/errcodes-appendix.html). While here, I switched out log for tracing.
19 lines
598 B
TOML
19 lines
598 B
TOML
[package]
|
|
name = "tokio-postgres2"
|
|
version = "0.1.0"
|
|
edition = "2024"
|
|
license = "MIT/Apache-2.0"
|
|
|
|
[dependencies]
|
|
bytes.workspace = true
|
|
fallible-iterator.workspace = true
|
|
futures-util = { workspace = true, features = ["sink"] }
|
|
tracing.workspace = true
|
|
parking_lot.workspace = true
|
|
pin-project-lite.workspace = true
|
|
postgres-protocol2 = { path = "../postgres-protocol2" }
|
|
postgres-types2 = { path = "../postgres-types2" }
|
|
tokio = { workspace = true, features = ["io-util", "time", "net"] }
|
|
tokio-util = { workspace = true, features = ["codec"] }
|
|
serde = { workspace = true, features = ["derive"] }
|