forked from mtusi2026/mtusi2026lab5
- RabbitMQ quorum queue, persistent messages and publisher confirms - S3 staging plus PostgreSQL attachments/jobs outbox transaction - worker variants (thumbnail, crop, optimized WebP), DB lease and lease sweeper - jittered retry, permanent failures, explicit replay and admission cap - deterministic crash hooks, resilience script and evidence for grade 4 - async-aware custom tests, oversized pixel case, docs and changelog
24 lines
1.1 KiB
SQL
24 lines
1.1 KiB
SQL
-- ScheduleRetry records the transient reason on the job while it waits for the
|
|
-- next attempt. The original 0004 constraint only allowed error_code on failed
|
|
-- rows, so a jittered retry update was rejected and the broker redelivery was
|
|
-- then acknowledged as "busy", leaving the job processing until lease expiry.
|
|
-- Ready stays clean; failed stays explainable; queued/processing may carry the
|
|
-- most recent transient reason.
|
|
ALTER TABLE attachments
|
|
DROP CONSTRAINT IF EXISTS attachments_error_state;
|
|
ALTER TABLE attachments
|
|
ADD CONSTRAINT attachments_error_state CHECK (
|
|
(status = 'ready' AND error_code IS NULL) OR
|
|
(status = 'failed' AND error_code IS NOT NULL) OR
|
|
(status IN ('queued', 'processing'))
|
|
);
|
|
|
|
ALTER TABLE attachment_jobs
|
|
DROP CONSTRAINT IF EXISTS attachment_jobs_error_state;
|
|
ALTER TABLE attachment_jobs
|
|
ADD CONSTRAINT attachment_jobs_error_state CHECK (
|
|
(status = 'ready' AND error_code IS NULL) OR
|
|
(status = 'failed' AND error_code IS NOT NULL) OR
|
|
(status IN ('queued', 'processing'))
|
|
);
|