* Register a new custom WAL resource manager.
*
* Resource manager IDs must be globally unique across all extensions. Refer
- * to https://wiki.postgresql.org/wiki/CustomWALResourceManager to reserve a
+ * to https://wiki.postgresql.org/wiki/CustomWALResourceManagers to reserve a
* unique RmgrId for your extension, to avoid conflicts with other extension
* developers. During development, use RM_EXPERIMENTAL_ID to avoid needlessly
* reserving a new ID.
RegisterCustomRmgr must be called from the
extension module's _PG_init function.
While developing a new extension, use RM_EXPERIMENTAL_ID
- for
rmid. When you
ready to release the extension to
- users, reserve a new resource manager ID at the
+ for
rmid. When you
are ready to release the extension
+
to users, reserve a new resource manager ID at the
url="https://wiki.postgresql.org/wiki/CustomWALResourceManagers">Custom WAL
Resource Manager page.
will be logged at
LOG message level. They will appear in
the server log based on the log configuration set
- (See for more information),
+ (see for more information),
but will not be sent to the client regardless of
.
- one of the publications has no row filter.
+ One of the publications has no row filter.
- one of the publications was created using FOR ALL TABLES.
+ One of the publications was created using FOR ALL TABLES.
This clause does not allow row filters.
- one of the publications was created using
+ One of the publications was created using
FOR TABLES IN SCHEMA and the table belongs to
the referred schema. This clause does not allow row filters.
* Register a new custom WAL resource manager.
*
* Resource manager IDs must be globally unique across all extensions. Refer
- * to https://wiki.postgresql.org/wiki/CustomWALResourceManager to reserve a
+ * to https://wiki.postgresql.org/wiki/CustomWALResourceManagers to reserve a
* unique RmgrId for your extension, to avoid conflicts with other extension
* developers. During development, use RM_EXPERIMENTAL_ID to avoid needlessly
* reserving a new ID.