Deployed ef5a96228 to latest with MkDocs 1.6.1 and mike 2.2.0

Author: mongoose-im

latest/graphql-api/admin-graphql-doc.html

@@ -3285,6 +3285,17 @@
     </span>
   </a>
 
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#modulesmod_pubsubmax_items_per_node" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        modules.mod_pubsub.max_items_per_node
+      
+    </span>
+  </a>
+  
 </li>
 
           <li class="md-nav__item">
@@ -5571,6 +5582,17 @@
     </span>
   </a>
 
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#modulesmod_pubsubmax_items_per_node" class="md-nav__link">
+    <span class="md-ellipsis">
+      
+        modules.mod_pubsub.max_items_per_node
+      
+    </span>
+  </a>
+  
 </li>
 
           <li class="md-nav__item">
@@ -5649,7 +5671,7 @@ <h3 id="node-configuration-options">Node configuration options<a class="headerli
 <p><code>mod_pubsub</code> supports the following node configuration and publish options:</p>
 <ul>
 <li><a href="https://xmpp.org/extensions/xep-0060.html#accessmodels"><code>pubsub#access_model</code></a>: controls who can access a node. Supported values are <code>open</code> and <code>presence</code>.</li>
-<li><code>pubsub#max_items</code>: controls how many published items are stored for later retrieval. It defaults to <code>max</code>, which stores all published items. A non-negative integer limits stored items for the node; when the limit is exceeded, the oldest stored item is removed. <code>0</code> allows publish notifications but does not persist items for later retrieval.</li>
+<li><code>pubsub#max_items</code>: controls how many published items are stored for later retrieval. It defaults to <code>max</code>, which stores all published items up to the server-wide <a href="#modulesmod_pubsubmax_items_per_node"><code>max_items_per_node</code></a> limit. A non-negative integer limits stored items for the node; when the limit is exceeded, the oldest stored item is removed. <code>0</code> allows publish notifications but does not persist items for later retrieval.</li>
 </ul>
 <h3 id="known-omissions-and-limitations">Known omissions and limitations<a class="headerlink" href="#known-omissions-and-limitations" title="Permanent link">&para;</a></h3>
 <p><code>mod_pubsub</code> is intended to grow over time, but it does not implement the full XEP-0060 feature set yet.
@@ -5669,6 +5691,15 @@ <h3 id="modulesmod_pubsubbackend"><code>modules.mod_pubsub.backend</code><a clas
 </ul>
 <p>Database backend used to store PEP nodes, subscriptions, and items.
 The <code>rdbms</code> backend requires a <code>default</code> RDBMS connection pool in <a href="../../configuration/outgoing-connections/#rdbms-options"><code>outgoing_pools</code></a>.</p>
+<h3 id="modulesmod_pubsubmax_items_per_node"><code>modules.mod_pubsub.max_items_per_node</code><a class="headerlink" href="#modulesmod_pubsubmax_items_per_node" title="Permanent link">&para;</a></h3>
+<ul>
+<li><strong>Syntax:</strong> non-negative integer or <code>"infinity"</code></li>
+<li><strong>Default:</strong> <code>"infinity"</code></li>
+<li><strong>Example:</strong> <code>max_items_per_node = 1000</code></li>
+</ul>
+<p>Maximum number of items stored in a node.
+The effective limit is the lower of this value and <code>pubsub#max_items</code>.
+If you reduce this limit, excess items for each already existing node are removed when it is next configured or receives a published item.</p>
 <h3 id="modulesmod_pubsubiqdisctype"><code>modules.mod_pubsub.iqdisc.type</code><a class="headerlink" href="#modulesmod_pubsubiqdisctype" title="Permanent link">&para;</a></h3>
 <ul>
 <li><strong>Syntax:</strong> string, one of <code>"one_queue"</code>, <code>"no_queue"</code>, <code>"queues"</code>, <code>"parallel"</code></li>