PostgreSQL vs Snowflake: reliability
In the last 60 days, PostgreSQL had 7 incidents and Snowflake had 5 incidents (median fix 42 min). Snowflake broke less often.
Side by side, last 60 days
| Measure | PostgreSQL | Snowflake |
|---|---|---|
| Incidents (60 days) | 7 | 5 |
| Critical or high | 3 | 0 |
| Median time to fix | n/a | 42 min |
| Longest incident | n/a | 9 h |
| Never on its status page | n/a | 0 |
| Status page delay (median) | n/a | 1 min |
| 30-day hazard rating | 5.6 / 10 | 3.8 / 10 |
PostgreSQL's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| PostgreSQL Multiple High-Severity Vulnerabilities (CVE-2026-116304 through CVE-2026-116325) Cause: Type confusion, use-after-free, heap-based buffer overflow, improper protection of alternate paths, untrusted search path issues, improper input validation, and SQL injection across various PostgreSQL internal components and utilities. | high | ongoing | ||
| PostgreSQL 22-Year-Old Type-Confusion Primitive Turned into Remote Code Execution Cause: A type-confusion primitive present for 22 years was exploited to achieve remote code execution. | high | ongoing | ||
| Postgres recovery_prefetch can cause outages Cause: recovery_prefetch feature misbehaved during recovery process | high | ongoing | ||
| Postgres Lock Queue Migration Outage Discussion | medium | ongoing | ||
| PostgreSQL Primary Cancel Commits Impact Async Replica Lag Cause: The async replica database was lagging behind the PostgreSQL primary, causing read operations to access stale data. | medium | ongoing |
Snowflake's worst incidents
| Date | Incident | Severity | Time to fix | Status page |
|---|---|---|---|---|
| Snowflake: INC20000351 | medium | 9 h | first | |
| Snowflake: INC20000350 | medium | 42 min | first | |
| Snowflake: INC20000347 | medium | 33 min | first | |
| Snowflake: INC20000337 | medium | 2 h | first | |
| Snowflake: INC20000336 | medium | 1 min | first |