Sorry ... it stores content in the content repository. There's no separate ordering key for file storage as in the 3.x version. In the PG version we don't have connect by queries so use sort keys to order query results when we want a hierarchical view. This key needs to be updated whenever an item is inserted, updated, or deleted. However the triggers are *much* smarter than fs_order_files and only affect a subset of the rows in the content repository tables.
