Three parameters have been using "int" rather than "integer" to describe
their type:
auth_delay.milliseconds
max_logical_replication_workers
pg_prewarm.autoprewarm_interval
This is inconsistent with any other integer GUCs listed in the docs
(148, as far as I can see).
Author: Peter Smith
Discussion: https://postgr.es/m/CAHut+Pv6X5T-veN2abUDUvBxZm+SSm-9otfi3LZPGyOc6u6hiA@mail.gmail.com
<variablelist>
<varlistentry>
<term>
- <varname>auth_delay.milliseconds</varname> (<type>int</type>)
+ <varname>auth_delay.milliseconds</varname> (<type>integer</type>)
<indexterm>
<primary><varname>auth_delay.milliseconds</varname> configuration parameter</primary>
</indexterm>
<variablelist>
<varlistentry id="guc-max-logical-replication-workers" xreflabel="max_logical_replication_workers">
- <term><varname>max_logical_replication_workers</varname> (<type>int</type>)
+ <term><varname>max_logical_replication_workers</varname> (<type>integer</type>)
<indexterm>
<primary><varname>max_logical_replication_workers</varname> configuration parameter</primary>
</indexterm>
<variablelist>
<varlistentry>
<term>
- <varname>pg_prewarm.autoprewarm_interval</varname> (<type>int</type>)
+ <varname>pg_prewarm.autoprewarm_interval</varname> (<type>integer</type>)
<indexterm>
<primary><varname>pg_prewarm.autoprewarm_interval</varname> configuration parameter</primary>
</indexterm>