summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/src/sgml/datatype.sgml2
-rw-r--r--doc/src/sgml/logicaldecoding.sgml8
-rw-r--r--doc/src/sgml/monitoring.sgml10
-rw-r--r--doc/src/sgml/ref/alter_table.sgml11
-rw-r--r--doc/src/sgml/regress.sgml63
-rw-r--r--doc/src/sgml/xfunc.sgml2
6 files changed, 65 insertions, 31 deletions
diff --git a/doc/src/sgml/datatype.sgml b/doc/src/sgml/datatype.sgml
index 0994e089311..7458f216e50 100644
--- a/doc/src/sgml/datatype.sgml
+++ b/doc/src/sgml/datatype.sgml
@@ -117,7 +117,7 @@
<row>
<entry><type>double precision</type></entry>
- <entry><type>float8</type></entry>
+ <entry><type>float</type>, <type>float8</type></entry>
<entry>double precision floating-point number (8 bytes)</entry>
</row>
diff --git a/doc/src/sgml/logicaldecoding.sgml b/doc/src/sgml/logicaldecoding.sgml
index 593f784b69d..77c720c422c 100644
--- a/doc/src/sgml/logicaldecoding.sgml
+++ b/doc/src/sgml/logicaldecoding.sgml
@@ -290,7 +290,7 @@ postgres=# select * from pg_logical_slot_get_changes('regression_slot', NULL, NU
<para>
A logical slot will emit each change just once in normal operation.
The current position of each slot is persisted only at checkpoint, so in
- the case of a crash the slot may return to an earlier LSN, which will
+ the case of a crash the slot might return to an earlier LSN, which will
then cause recent changes to be sent again when the server restarts.
Logical decoding clients are responsible for avoiding ill effects from
handling the same message more than once. Clients may wish to record
@@ -409,7 +409,7 @@ postgres=# select * from pg_logical_slot_get_changes('regression_slot', NULL, NU
should be used with caution. Unlike automatic synchronization, it does not
include cyclic retries, making it more prone to synchronization failures,
particularly during initial sync scenarios where the required WAL files
- or catalog rows for the slot may have already been removed or are at risk
+ or catalog rows for the slot might have already been removed or are at risk
of being removed on the standby. In contrast, automatic synchronization
via <varname>sync_replication_slots</varname> provides continuous slot
updates, enabling seamless failover and supporting high availability.
@@ -430,8 +430,8 @@ postgres=# select * from pg_logical_slot_get_changes('regression_slot', NULL, NU
standby, the slot will not be persisted to avoid data loss. In such
cases, the following log message may appear:
<programlisting>
- LOG: could not synchronize replication slot "failover_slot"
- DETAIL: Synchronization could lead to data loss as the remote slot needs WAL at LSN 0/03003F28 and catalog xmin 754, but the standby has LSN 0/03003F28 and catalog xmin 756
+LOG: could not synchronize replication slot "failover_slot"
+DETAIL: Synchronization could lead to data loss, because the remote slot needs WAL at LSN 0/03003F28 and catalog xmin 754, but the standby has LSN 0/03003F28 and catalog xmin 756.
</programlisting>
If the logical replication slot is actively used by a consumer, no
manual intervention is needed; the slot will advance automatically,
diff --git a/doc/src/sgml/monitoring.sgml b/doc/src/sgml/monitoring.sgml
index fa78031ccbb..3f4a27a736e 100644
--- a/doc/src/sgml/monitoring.sgml
+++ b/doc/src/sgml/monitoring.sgml
@@ -6791,6 +6791,16 @@ FROM pg_stat_get_backend_idset() AS backendid;
advances when the phase is <literal>streaming database files</literal>.
</para></entry>
</row>
+
+ <row>
+ <entry role="catalog_table_entry"><para role="column_definition">
+ <structfield>backup_type</structfield> <type>text</type>
+ </para>
+ <para>
+ Backup type. Either <literal>full</literal> or
+ <literal>incremental</literal>.
+ </para></entry>
+ </row>
</tbody>
</tgroup>
</table>
diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml
index 541e093a519..8867da6c693 100644
--- a/doc/src/sgml/ref/alter_table.sgml
+++ b/doc/src/sgml/ref/alter_table.sgml
@@ -210,6 +210,8 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
When this form is used, the column's statistics are removed,
so running <link linkend="sql-analyze"><command>ANALYZE</command></link>
on the table afterwards is recommended.
+ For a virtual generated column, <command>ANALYZE</command>
+ is not necessary because such columns never have statistics.
</para>
</listitem>
</varlistentry>
@@ -271,6 +273,15 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
in a stored generated column is rewritten and all the future changes
will apply the new generation expression.
</para>
+
+ <para>
+ When this form is used on a stored generated column, its statistics
+ are removed, so running
+ <link linkend="sql-analyze"><command>ANALYZE</command></link>
+ on the table afterwards is recommended.
+ For a virtual generated column, <command>ANALYZE</command>
+ is not necessary because such columns never have statistics.
+ </para>
</listitem>
</varlistentry>
diff --git a/doc/src/sgml/regress.sgml b/doc/src/sgml/regress.sgml
index bf4ffb30576..8838fe7f022 100644
--- a/doc/src/sgml/regress.sgml
+++ b/doc/src/sgml/regress.sgml
@@ -285,75 +285,88 @@ make check-world PG_TEST_EXTRA='kerberos ldap ssl load_balance libpq_encryption'
</varlistentry>
<varlistentry>
- <term><literal>sepgsql</literal></term>
+ <term><literal>libpq_encryption</literal></term>
<listitem>
<para>
- Runs the test suite under <filename>contrib/sepgsql</filename>. This
- requires an SELinux environment that is set up in a specific way; see
- <xref linkend="sepgsql-regression"/>.
+ Runs the test <filename>src/interfaces/libpq/t/005_negotiate_encryption.pl</filename>.
+ This opens TCP/IP listen sockets. If <varname>PG_TEST_EXTRA</varname>
+ also includes <literal>kerberos</literal>, additional tests that require
+ an MIT Kerberos installation are enabled.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>ssl</literal></term>
+ <term><literal>load_balance</literal></term>
<listitem>
<para>
- Runs the test suite under <filename>src/test/ssl</filename>. This opens TCP/IP listen sockets.
+ Runs the test <filename>src/interfaces/libpq/t/004_load_balance_dns.pl</filename>.
+ This requires editing the system <filename>hosts</filename> file and
+ opens TCP/IP listen sockets.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>load_balance</literal></term>
+ <term><literal>oauth</literal></term>
<listitem>
<para>
- Runs the test <filename>src/interfaces/libpq/t/004_load_balance_dns.pl</filename>.
- This requires editing the system <filename>hosts</filename> file and
- opens TCP/IP listen sockets.
+ Runs the test suite under <filename>src/test/modules/oauth_validator</filename>.
+ This opens TCP/IP listen sockets for a test server running HTTPS.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>libpq_encryption</literal></term>
+ <term><literal>regress_dump_restore</literal></term>
<listitem>
<para>
- Runs the test <filename>src/interfaces/libpq/t/005_negotiate_encryption.pl</filename>.
- This opens TCP/IP listen sockets. If <varname>PG_TEST_EXTRA</varname>
- also includes <literal>kerberos</literal>, additional tests that require
- an MIT Kerberos installation are enabled.
+ Runs an additional test suite in
+ <filename>src/bin/pg_upgrade/t/002_pg_upgrade.pl</filename> which
+ cycles the regression database through <command>pg_dump</command>/
+ <command>pg_restore</command>. Not enabled by default because it
+ is resource intensive.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>wal_consistency_checking</literal></term>
+ <term><literal>sepgsql</literal></term>
<listitem>
<para>
- Uses <literal>wal_consistency_checking=all</literal> while running
- certain tests under <filename>src/test/recovery</filename>. Not
- enabled by default because it is resource intensive.
+ Runs the test suite under <filename>contrib/sepgsql</filename>. This
+ requires an SELinux environment that is set up in a specific way; see
+ <xref linkend="sepgsql-regression"/>.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>xid_wraparound</literal></term>
+ <term><literal>ssl</literal></term>
<listitem>
<para>
- Runs the test suite under <filename>src/test/modules/xid_wraparound</filename>.
- Not enabled by default because it is resource intensive.
+ Runs the test suite under <filename>src/test/ssl</filename>. This opens TCP/IP listen sockets.
</para>
</listitem>
</varlistentry>
<varlistentry>
- <term><literal>oauth</literal></term>
+ <term><literal>wal_consistency_checking</literal></term>
<listitem>
<para>
- Runs the test suite under <filename>src/test/modules/oauth_validator</filename>.
- This opens TCP/IP listen sockets for a test server running HTTPS.
+ Uses <literal>wal_consistency_checking=all</literal> while running
+ certain tests under <filename>src/test/recovery</filename>. Not
+ enabled by default because it is resource intensive.
+ </para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
+ <term><literal>xid_wraparound</literal></term>
+ <listitem>
+ <para>
+ Runs the test suite under <filename>src/test/modules/xid_wraparound</filename>.
+ Not enabled by default because it is resource intensive.
</para>
</listitem>
</varlistentry>
diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml
index 2d81afce8cb..30219f432d9 100644
--- a/doc/src/sgml/xfunc.sgml
+++ b/doc/src/sgml/xfunc.sgml
@@ -2165,7 +2165,7 @@ memcpy(destination->data, buffer, 40);
it's considered good style to use the macro <literal>VARHDRSZ</literal>
to refer to the size of the overhead for a variable-length type.
Also, the length field <emphasis>must</emphasis> be set using the
- <literal>SET_VARSIZE</literal> macro, not by simple assignment.
+ <literal>SET_VARSIZE</literal> function, not by simple assignment.
</para>
<para>
generated by cgit v1.2.3 (git 2.39.1) at 2025-08-08 01:04:26 +0000