Burak Yucesoy 1a5fa3e082 Fix broken billing record index ...

We have a partial unique constraint on the resource_id of the billing_record
table. However, the index was created with wrong condition. Its condition is
`WHERE span(upper) = NULL`, which is always false, because in the SQL standard
comparison against NULL always returns NULL which is evaluated as false. The
correct form should have been `WHERE span(upper) is NULL`. This means that the
index is not used at all. We didn't realized this, because we stopped caring
about uniqueness of resource_id in the billing_record table for a while as one
resource can have multiple active billing records (for different parts of the
resource such as compute and storage).

As a fix, I'm recreating the index without the condition. Also I put noop for
down migration, because the previous state of the DB also had the index (alas
with wrong condition).

2024-05-31 18:17:34 +03:00

230 B

Raw Permalink Blame History

View Raw