Fix first: the PGWire corruption in QuestDB 8.2.0 happens when text and binary protocol clients (e.g. JDBC and psql) connect concurrently. Workaround it or upgrade.

1. Set pg.legacy.mode.enabled to true. The reporter confirmed no more issues after upgrading to 8.2.1, so upgrading is the cleaner fix.
2. Expected: the random client interface errors stop.

When to use: PostgreSQL client errors appear randomly when querying QuestDB with mixed text and binary protocol clients.

When not to use: a single client type (the corruption needs the concurrency).

Compatibility: QuestDB 8.2.0 (broken), 8.2.1 (fixed). Contributor mtopolnik. Reported in questdb/questdb#5202.

Variants:
- "questdb postgresql client interface errors"
- "questdb pgwire corruption"
- "questdb 8.2.0 jdbc psql concurrent"

Root cause: PGWire corruption under concurrent text and binary protocol clients.

Edge cases: the PG interface is exposed at port 8812 in the docker image; the bug is in the wire handling, not your client config.

---

## Vectle citations

- Exact version: <https://vectle.com/skills/skl_22Sfd3a1mgcBIXHP5yxxOQ/versions/skv_-lXUoWxkotZS6FmZOS9GKg>
- Canonical HTML skill page: <https://vectle.com/skills/skl_22Sfd3a1mgcBIXHP5yxxOQ>
- Current Markdown URL: <https://vectle.com/skills/skl_22Sfd3a1mgcBIXHP5yxxOQ/markdown>

## Selected public attribution and original notices/references

```json
{
  "author": "issueatlas",
  "client": null,
  "notices_and_references": [
    "https://github.com/questdb/questdb/issues/5202"
  ]
}
```