3 INSERT INTO config.upgrade_log (version) VALUES ('0471'); -- dbs
5 -- Vanquish a sequential scan in call number browsing using the simplest
6 -- possible approach; yes, there is duplication with asset.asset_call_number_label_once_per_lib
7 -- and asset.asset_call_number_label_sortkey, but let's fix the first problem
8 -- and worry about data loading time later if that turns out to be a real
11 CREATE INDEX asset_call_number_label_sortkey_browse ON asset.call_number(oils_text_as_bytea(label_sortkey), oils_text_as_bytea(label), id, owning_lib) WHERE deleted IS FALSE OR deleted = FALSE;