v0.32.0

Added

• riverlog.Middleware now supports MiddlewareConfig.MaxTotalBytes (default 8 MB) to cap total persisted river:log history per job. When the cap is exceeded, oldest log entries are dropped first while retaining the newest entry. Values over 64 MB are clamped to 64 MB. PR #1157.

Changed

• Improved riverlog performance and reduced memory amplification when appending to large persisted river:log histories. PR #1157.
• Reduced snooze-path memory amplification by setting snoozes in metadata updates before marshaling, avoiding an extra full-payload JSON rewrite. PR #1159.
• Schema names are now quoted in SQL operations, enabling the use of spaces and other odd characters. PR #1175.

Fixed

• riverpgxv5 now adapts JSON parameters for simple protocol / exec query modes so []byte JSON payloads are not encoded as bytea in pgx text-mode execution paths. This fixes invalid JSON syntax errors when running through protocol-constrained setups like PgBouncer transaction pooling while preserving normal behavior for explicit bytea parameters. Fixes #1153. PR #1155.