This article describes an issue which you may come across in versions before Vesper 6.0. It has been resolved in Vesper 6.1.
...
Check if there are really any missing indexes.
Indexes in PostgreSQL are created based on the Datamart configuration. Fields marked as dimension should have corresponding indexes.
Example: In the DB table for the Product DS, we expect an index on the column representing the key field in the DS:Paste code macro Column | Type | Description ---------------+-----------------------------+--------------------------------- attribute1 | character varying(255) | ProductID/Product ID Index: "abc-dev_DMDS_Product_uniq_upsert_idx" UNIQUE, btree (attribute1)
- Check if you see generally much worse performance in your environment after upgrade to Vesper 6.0.
If the index is missing, queries and hence jobs are slower, and as a knock-on effect, the DB connection limit can be reached where previously it was not.
...
- Deploy Vesper 6.1.
Run this command in the system partition
- Set Partition: system
Set Real URL (modify abc-qa to relevant partition label):
Code Block system$redeployfcs/abc-qa/createIndices