database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-10-16 17:07:43 +03:00
Code Activity

Rename XLogData protocol message to WALData

Browse Source 
This name is only used as documentation, and using this name is
consistent with its byte being a 'w'.  Renaming it would also make the
use of a symbolic name based on the word "WAL" rather than the obsolete
"XLog" term more consistent, per future commits along the lines of
37c7a7eeb6, 4a68d50088, f4b54e1ed9.

Discussion: https://postgr.es/m/aIECfYfevCUpenBT@nathan
This commit is contained in:
Álvaro Herrera
2025-08-04 14:03:01 +02:00
parent 4614d53d4e
commit 07684443b1
3 changed files with 15 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
doc/src/sgml/protocol.sgml
View File

@@ -2555,8 +2555,8 @@ psql "dbname=postgres replication=database" -c "IDENTIFY_SYSTEM;"
</para>
<variablelist>
<varlistentry id="protocol-replication-xlogdata">
<term>XLogData (B)</term>
<varlistentry id="protocol-replication-waldata">
<term>WALData (B)</term>
<listitem>
<variablelist>
<varlistentry>
@@ -2604,11 +2604,11 @@ psql "dbname=postgres replication=database" -c "IDENTIFY_SYSTEM;"
</para>
<para>
A single WAL record is never split across two XLogData messages.
A single WAL record is never split across two WALData messages.
When a WAL record crosses a WAL page boundary, and is therefore
already split using continuation records, it can be split at the page
boundary. In other words, the first main WAL record and its
continuation records can be sent in different XLogData messages.
continuation records can be sent in different WALData messages.
</para>
</listitem>
</varlistentry>