Note for self-hosted customers
v374 includes a database migration that significantly improves application performance by moving from JSON blobs to a more normalized form.
Because of this migration, Textual services will be unavailable during the upgrade. The process takes only a few minutes for most customers, but can take up to several hours for organizations that have specific data profiles.
To determine the migration time, review the number of rows in the DeidentifyFileRowResults table. To determine the number of rows in this table, connect to your PostgreSQL metadata database and run
SELECT count(*) from "DeidentifyFileRowResults";
If the count is higher than 300,000 rows, expect the migration to take several hours.
To decrease the number of rows in this table, in your datasets, delete any CSV or XLSX files that you no longer use. These file types add a disproportionate number of rows to this table.
If you need any assistance, reach out to Tonic.ai.
