NO-JIRA Doc update database store

docs/user-manual/en/persistence.md

@@ -431,6 +431,7 @@ To configure Apache ActiveMQ Artemis to use a database for persisting messages a
             <jdbc-connection-url>jdbc:derby:data/derby/database-store;create=true</jdbc-connection-url>
             <bindings-table-name>BINDINGS_TABLE</bindings-table-name>
             <message-table-name>MESSAGE_TABLE</message-table-name>
+            <page-store-table-name>MESSAGE_TABLE</page-store-table-name>
             <large-message-table-name>LARGE_MESSAGES_TABLE</large-message-table-name>
             <jdbc-driver-class-name>org.apache.derby.jdbc.EmbeddedDriver</jdbc-driver-class-name>
          </database-store>
@@ -453,10 +454,15 @@ To configure Apache ActiveMQ Artemis to use a database for persisting messages a
 
     The name of the table in which messages and related data will be persisted for the ActiveMQ Artemis server.  Specifying table names allows users to share single database amongst multiple servers, without interference.
     
+-   `page-store-table-name`
+
+    The name of the table to house the page store directory information.  Note that each address will have it's own page table which will use this name appended with a unique id of up to 20 characters.
+
 -   `jdbc-driver-class-name`
 
     The fully qualified class name of the desired database Driver.
 
+Note that some DBMS (e.g. Oracle, 30 chars) have restrictions on the size of table names, this should be taken into consideration when configuring table names for the Artemis database store, pay particular attention to the page store table name, which can be appended with a unique ID of up to 20 characters.  (for Oracle this would mean configuring a page-store-table-name of max size of 10 chars).
 
 ## Configuring Apache ActiveMQ Artemis for Zero Persistence