You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
What's fixed
A SUM or AVG that fell into NaN was stuck, we now track and repair this (see #1756, #1763)
If you have any targets that are already stuck, you'll need to request_backfill on them. You can use self_check to check for this stuck state
Unique expression indexes no longer qualify as a keyspace definition (see #1725)
self_check had a false-positive case for aggregates with active data changes which was fixed (see #1688)
Upgrading from 0.1.0
Stop every 0.1.0 process before you start 0.1.1. Releases before 0.2.0 have no version handover, so two of them must never run on one database at the same time. Stop every worker and every handle, deploy 0.1.1, then start it.
This will be improved in the 0.2.0 release to automatically standby until the old processes stop
Rolling back to 0.1.0: with no migration, 0.1.0 opens a database 0.1.1 has run. One exception: 0.1.1 stores a numeric(p,s) sum that counts a NaN as the finite values plus 10^2100 per NaN, and 0.1.0 reads that as a 2,100-digit sum once the group is next written (until then the visible value stays correct). Running request_backfill under 0.1.1 doesn't help, because 0.1.1's rebuild writes the same encoding again. After rolling back, run request_backfill under 0.1.0 on every source with a numeric(p,s)SUM/AVG that holds a NaN, ideally before writes reach it; this also repairs a group that already shows the 2,100-digit sum.
Known issues in the 0.1 line, fixed in 0.2.0
On PostgreSQL 18, a definition reading a virtual generated column makes every insert into its source fail (#1570). Make the column STORED, or don't read it.
ALTER COLUMN … SET EXPRESSION on a stored generated column that a definition reads rewrites its values with no trigger, so the readers stay live and stale (#1540). Run request_backfill on the table afterwards.
A source key column re-collated after define, between deterministic collations, can make a rebuild or self_check fail with "could not determine which collation to use". This covers a part of a composite 1-1 key (#1537), an aggregate JOIN's GROUP BY column (#1558) and an aggregate JOIN's ON column on one side (#1564). The failure is loud, never silent. The remedy is DROP TRANSFORM and define again.
A source key with INCLUDE columns is taken as keyed by those columns too (#1722). A deferrable primary key is accepted as a table's key (#1742).