[quote]
Yes!!! Chris, thank you! It's down to 3.1GB now.
OK, just a couple of things to polish off, but then I don't know how serious these are:
Some tables have incorrect names for primary keys.
This won't cause any problems, but upgrade guides may be harder to follow
as they expect the names to be a certain way.
To fix these tables, run the following commands
They can take a while depending on the size of the table.
BEGIN;
ALTER TABLE ONLY sq_ast_attr_val DROP CONSTRAINT sq_ast_attr_val_pkey;
ALTER TABLE sq_ast_attr_val ADD CONSTRAINT ast_attr_val_pk PRIMARY KEY (assetid,attrid,contextid);
ALTER TABLE ONLY sq_rb_ast_attr_val DROP CONSTRAINT sq_rb_ast_attr_val_pkey;
ALTER TABLE sq_rb_ast_attr_val ADD CONSTRAINT rb_ast_attr_val_pk PRIMARY KEY (sq_eff_from,assetid,attrid,contextid);
ALTER TABLE ONLY sq_ast_attr_uniq_val DROP CONSTRAINT sq_ast_attr_uniq_val_pkey;
ALTER TABLE sq_ast_attr_uniq_val ADD CONSTRAINT ast_attr_uniq_val_pk PRIMARY KEY (owning_attrid,contextid,custom_val);
ALTER TABLE ONLY sq_rb_ast_attr_uniq_val DROP CONSTRAINT sq_rb_ast_attr_uniq_val_pkey;
ALTER TABLE sq_rb_ast_attr_uniq_val ADD CONSTRAINT rb_ast_attr_uniq_val_pk PRIMARY KEY (sq_eff_from,owning_attrid,contextid,custom_val);
ALTER TABLE ONLY sq_ast_mdata_val DROP CONSTRAINT sq_ast_mdata_val_pkey;
ALTER TABLE sq_ast_mdata_val ADD CONSTRAINT ast_mdata_val_pk PRIMARY KEY (assetid,fieldid,contextid);
ALTER TABLE ONLY sq_rb_ast_mdata_val DROP CONSTRAINT sq_rb_ast_mdata_val_pkey;
ALTER TABLE sq_rb_ast_mdata_val ADD CONSTRAINT rb_ast_mdata_val_pk PRIMARY KEY (sq_eff_from,assetid,fieldid,contextid);
ALTER TABLE ONLY sq_ast_mdata_dflt_val DROP CONSTRAINT sq_ast_mdata_dflt_val_pkey;
ALTER TABLE sq_ast_mdata_dflt_val ADD CONSTRAINT ast_mdata_dflt_val_pk PRIMARY KEY (assetid,contextid);
ALTER TABLE ONLY sq_rb_ast_mdata_dflt_val DROP CONSTRAINT sq_rb_ast_mdata_dflt_val_pkey;
ALTER TABLE sq_rb_ast_mdata_dflt_val ADD CONSTRAINT rb_ast_mdata_dflt_val_pk PRIMARY KEY (sq_eff_from,assetid,contextid);
ALTER TABLE ONLY sq_sch_idx DROP CONSTRAINT sq_sch_idx_pkey;
ALTER TABLE sq_sch_idx ADD CONSTRAINT sch_idx_pk PRIMARY KEY (value,assetid,component,contextid);
COMMIT;
------------------------------------
------------------------------------
Extra indexes have been found on the following tables.
If these changes have been made deliberately, ignore this warning.
This can lead to performance loss.
To remove these, run the following command(s):
These were found on table sq_ast_attr_val:
DROP INDEX sq_ast_attr_val_contextid;
These were found on table sq_internal_msg:
DROP INDEX sq_internal_msg_userto;
------------------------------------
Is this something I acutally missed during previous upgrades or should I ignore this?
Sorry about the amount of text, but i though it would be best to just output everything.
Thank you all!
[/quote]
Those index changes are just a naming thing. Matrix is looking for 'ast_attr_val_pk' but found 'ast_attr_val_pkey' instead. It's not going to affect anything right now but may later if an upgrade looks for 'ast_attr_val_pk' to change the primary key of the table, it won't be able to find it.
Dropping those extra indexes at the end should speed up particular actions on those tables (insert/update/deletes).
