>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3586862. --> Reported by: [ignacio.perez.puertas@gmail.com](https://www.drupal.org/user/3637006) Related to !24 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>Clearing and reindexing an <code>ai_search</code> index whose backend uses <code>database: postgres</code> recreates the collection table without the<br> columns previously added for fields configured as <strong>Attributes</strong> in <code>ai_search.index.&amp;lt;id&amp;gt;.indexing_options</code>. The next batch<br> of inserts fails with:</p> <pre><pre>column "&amp;lt;attribute&amp;gt;" of relation "&amp;lt;collection&amp;gt;" does not exist<br>&nbsp; </pre></pre><p>Reproducible with any field marked as Attributes (for example <code>langcode</code>, <code>status</code>) on a multilingual or permissions-aware index.<br> Tested on Drupal 11, ai 1.3.3, ai_search 1.3.0-alpha1, ai_vdb_provider_postgres 1.0.0-alpha3, PostgreSQL 17 + pgvector 0.8.2.</p> <h4 id="summary-steps-reproduce">Steps to reproduce</h4> <ol> <li>Configure an <code>ai_search</code> index <code>content_rag</code> with backend <code>postgres</code>.</li> <li>In the index "Indexing options" tab, mark one or more <code>search_api</code> fields as <strong>Attributes</strong> (for example <code>langcode</code><br> and <code>status</code>).</li> <li>Save. The hook <code>ai_vdb_provider_postgres_search_api_index_update()</code> fires and <code>PostgresPgvectorClient::updateFields()</code> adds the<br> columns. Indexing succeeds.</li> <li>Trigger a clear+reindex via any path that funnels through <code>SearchApiAiSearchBackend::deleteAllIndexItems()</code>:<br> <pre>drush search-api:clear<br>&nbsp; &amp;amp;&amp;amp; drush search-api:index</pre><p>, the "Clear all indexed data" button in the UI, or any equivalent.</p></li> <li>The first batch of inserts fails as quoted above.</li> </ol> <p>Manual workaround until a release ships, run after each clear+reindex:</p> <pre><pre>ALTER TABLE content_rag ADD COLUMN IF NOT EXISTS langcode VARCHAR;<br>&nbsp; ALTER TABLE content_rag ADD COLUMN IF NOT EXISTS status&nbsp;&nbsp; BOOLEAN;<br>&nbsp; </pre></pre><p>Replace with the postgres types from <code>PostgresPgvectorClient::DATA_TYPE_MAPPING</code> for whichever fields are marked as Attributes.</p> <h4 id="summary-root-cause">Root cause</h4> <p><code>Drupal\ai\Base\AiVdbProviderClientBase::deleteAllIndexItems(array $configuration, IndexInterface $index, $datasource_id = NULL)</code> receives<br> <code>$index</code> from <code>SearchApiAiSearchBackend::deleteAllIndexItems()</code> but discards it when delegating to<br> <code>deleteAllItems($configuration, $datasource_id)</code>, which executes:</p> <ul> <li><code>dropCollection()</code> issuing <code>DROP TABLE IF EXISTS ... CASCADE;</code></li> <li><code>createCollection()</code> issuing<br> <pre>CREATE TABLE ... (id, content, drupal_entity_id, drupal_long_id, server_id, index_id, embedding<br>&nbsp; vector(N));</pre></li> </ul> <p>The recreated table only contains native columns. The Attributes columns added previously via <code>updateFields()</code> are gone. The hook calling<br> <code>updateFields()</code> only fires on <code>hook_search_api_index_update</code>, i.e. on index config changes, not on a clear+reindex cycle.</p> <p><code>PostgresProvider</code> already overrides <code>deleteAllItems()</code> to re-apply <code>ensureVectorIndex()</code> after the drop+create cycle<br> (HNSW/IVFFlat get restored), but no equivalent restoration exists for Attributes columns.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Override <code>deleteAllIndexItems()</code> in <code>PostgresProvider</code> so it re-applies<br> <code>PostgresPgvectorClient::updateFields($index-&amp;gt;getFields(), ...)</code> after the parent's drop+create. The fix stays inside<br> <code>ai_vdb_provider_postgres</code> (the only provider in the AI ecosystem with a rigid schema, hence the only one affected) and leaves<br> <code>\Drupal\ai\AiVdbProviderInterface</code> untouched. <code>updateFields()</code> is idempotent (<code>ADD COLUMN IF NOT EXISTS</code>), so this is<br> also safe on the very first create path.</p> <p>Patch attached. Verified locally end-to-end on the stack listed above: after applying the patch and running </p> <pre>drush search-api:clear &amp;amp;&amp;amp;<br>&nbsp; drush search-api:index</pre><p>, the table retains all Attributes columns and the 6 test chunks index without errors. Pipeline retrieval against the rebuilt<br> collection returns expected results.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>Review the patch.</li> <li>Add a kernel/functional test that creates a postgres-backed <code>ai_search</code> index with at least one Attributes field, performs a clear+reindex,<br> and asserts the columns survive.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>None.</p> <h3 id="summary-api-changes">API changes</h3> <p>None. Adds an override in <code>PostgresProvider</code>; the public interface contract is unchanged.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>None. The columns the patch reapplies are already part of the documented data model when Attributes are configured; the patch only ensures they are not<br> silently lost during a clear+reindex.</p>