Confluence Docs 3.1 : Page Restrictions Performance Considerations
This page last changed on Nov 16, 2009 by jlargman.
Page Permissions and the Confluence Search IndexModifying the page permissions requires reindexing all child pages, as well as comments and attachments on all those pages. The reasons for this:
Therefore, to update an attachment record in the index, even just to change the permissions, the attachment's content must be reindexed. Performance ConsiderationsIn the large majority of situations, this design should not be a problem. In large spaces with deep page hierarchies, it might be. Use performance logging for the index flush operation to assess the impact of changing a page restriction - try it on the space's home page, or a page with a lot of children, to see the performance impact of changing a page restriction. Space Design ConsiderationsFor some space designs, deep page hierarchies may be desirable. If possible, it's recommended to split spaces where it makes sense to do so, according to how your information is organized. One workaround – CONF-7089 – involves opening up access to just a few pages in a mostly-restricted space so as to "open" the space where space permissions close it. This may be a performance concern if the space, and attachments in the space, are large. WorkaroundsThere are a few workarounds to consider:
Which Pages Have Restrictions?A database query to show which pages in your instance have page restrictions: SELECT DISTINCT content.contentid, content.TITLE as page_title, CONTENT_PERM.USERNAME as page_restriction_username, CONTENT_PERM.CP_TYPE as page_restriction_type FROM CONTENT_PERM, content WHERE CONTENTID IN (SELECT CONTENT_ID FROM CONTENT_PERM_SET WHERE ID IN (SELECT CPS_ID from CONTENT_PERM)) |
![]() |
Document generated by Confluence on Dec 10, 2009 18:46 |