Issue Summary

Confluence's default permission checking method is very efficient when checking permissions for a single page, and guarantees strong permission consistency. However, this method can be quite slow and memory intensive when Confluence needs to check many thousands of pages.

The faster permissions service solves this by replicates permissions information in a database structure that can be queried more efficiently. It uses database triggers to register changes to pages, spaces and their permissions, and records these in a change log. These change logs are processed regularly, and keep the fast permissions database tables up to date.

If these database tables become corrupted, page searches and macros, such as the children macros, may display inaccurate information.

Steps to Reproduce

For still unknown reasons, in some rare occasions, the Faster Permissions table can become corrupted.

Expected Results

Macros and features that use the "faster permissions" should display correct information

Actual Results

Page searches and macros, such as the children macros, display inaccurate information.

Workaround

The process to diagnose the issue and the workaround is described in detail in this article.

 Before applying the workaround, make sure you have a healthy ancestor table. Diagnostic query here.