sql
PostgreSQL WAL segment removed before replica consumed it
ERROR.*WAL.*segment.*not found|requested WAL segment.*has already been removed
Fixes
- 1.Use replication slots to retain WAL segments until replicas have consumed them
- 2.Increase wal_keep_size (or wal_keep_segments in older versions) to retain more WAL
- 3.Rebuild the replica from a fresh base backup if it's fallen too far behind
postgresqlreplicationWAL
Related Errors
sql3 fixes
PostgreSQL JSONB extracting from scalar
ERROR:.*cannot extract elements from a scalar.*jsonb
- •Check value is an object/array before extraction: jsonb_typeof(col) = 'object'
- •Use COALESCE with '{}' for null/scalar values
sql3 fixes
PostgreSQL JSONB operator type mismatch
ERROR:.*operator does not exist.*jsonb @> text
- •Cast the right operand to jsonb: col @> '{"key": "val"}'::jsonb
- •Use ->> operator for text extraction instead of ->
sql3 fixes
PostgreSQL full-text search config not found
ERROR:.*text search configuration.*does not exist
- •Create the text search configuration or use a built-in one (english, simple)
- •Install the pg_catalog extension if using a custom configuration