Skip to content

graph: Re-enable postponed index creation in debug builds#6614

Open
incrypto32 wants to merge 1 commit into
masterfrom
krishna/fix-postpone-tests
Open

graph: Re-enable postponed index creation in debug builds#6614
incrypto32 wants to merge 1 commit into
masterfrom
krishna/fix-postpone-tests

Conversation

@incrypto32
Copy link
Copy Markdown
Member

Follow-up to v0.44.0 (#6611): the disable patch hardcoded
postpone_attribute_index_creation to false, which broke CI in
relational::ddl_tests (generate_ddl, generate_postponed_indexes,
postponed_indexes_with_block_column).

Switching to cfg!(debug_assertions) keeps the production behavior
(release builds: postponement off, env var inert) and re-enables it
for debug builds so the tests pass.

The v0.44.0 disable patch hardcoded `postpone_attribute_index_creation`
to `false`, which broke three `relational::ddl_tests` (`generate_ddl`,
`generate_postponed_indexes`, `postponed_indexes_with_block_column`)
that exercise the postponed-index DDL path and relied on the prior
`cfg!(debug_assertions)` auto-on for that coverage.

Switch the field to `cfg!(debug_assertions)` so:

- Release builds (production): postponement stays off regardless of
  env var, matching the intent of the original disable.
- Debug builds (CI + dev): postponement is on, so the existing tests
  exercise the code path and pass.

The `GRAPH_POSTPONE_ATTRIBUTE_INDEX_CREATION` env var stays inert
(parsed but unused, hence the existing `#[allow(unused)]`).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant