Problem / Motivation
All errors surface as generic Postgres ERROR with no SQLSTATE differentiation. Applications can't programmatically distinguish connection failures from proto errors from gRPC call failures — they have to parse error message strings.
Proposed Solution
Map each GrpcError variant to an appropriate SQLSTATE code so applications can handle different failure types programmatically without string parsing.
Problem / Motivation
All errors surface as generic Postgres
ERRORwith no SQLSTATE differentiation. Applications can't programmatically distinguish connection failures from proto errors from gRPC call failures — they have to parse error message strings.Proposed Solution
Map each
GrpcErrorvariant to an appropriate SQLSTATE code so applications can handle different failure types programmatically without string parsing.