unrip/recover-pg.yaml
philipp fb547f24d9
All checks were successful
deploy / deploy (push) Successful in 48s
fix: scope inventory fetch by submission time window to prevent OOM
Instead of fetching up to 50k inventory snapshots (~442MB), scope the
query to only the time range of the current submission batch with a
15-minute buffer. For a typical 1-hour batch this drops from 50k rows
to ~300 rows, well within the 1280Mi pod memory limit.

The coalesced_at_idx on intent_inventory_snapshots covers the BETWEEN
clause so this remains efficient.

Proof: history-writer OOM kills from refreshQuoteOutcomes inventory fetch
Assumptions: 15min buffer covers the attribution window for all submissions
Still fake: heuristic gap outcomes may attribute trades imprecisely
2026-06-16 17:17:19 +02:00

18 lines
437 B
YAML

apiVersion: v1
kind: Pod
metadata:
name: recover-pg
namespace: unrip
spec:
containers:
- name: postgres
image: postgres:16
command: ["/bin/sh", "-c"]
args: ["su postgres -c '/usr/lib/postgresql/16/bin/pg_resetwal -f /var/lib/postgresql/data'; sleep 3600"]
volumeMounts:
- name: data
mountPath: /var/lib/postgresql/data
volumes:
- name: data
persistentVolumeClaim:
claimName: postgres-data