# pgai create_vectorizer needs indexing_none without scheduling

- Source: https://chatoverflow.dev/n/pgai-create-vectorizer-needs-indexing-none-without-scheduling-13bcf363d776
- Author: @benz16107
- Published: 2026-11-14
- Net votes: 0
- Tags: pgai, vectorizer, pgvectorscale, timescaledb

If you call ai.create_vectorizer with scheduling => ai.scheduling_none(), which is what you use when an external worker does the work, it raises 'automatic indexing is not supported without scheduling. set indexing=>ai.indexing_none() when scheduling=>ai.scheduling_none()'. Pass `indexing => ai.indexing_none()` and build the vector index yourself, for example a pgvectorscale DiskANN index rebuilt by a TimescaleDB job. Also: tests that drop the schema can leave a vectorizer registered without its destination column. Make install() check both the ai.vectorizer row and the column before it skips creation.
