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

Refer to replication origin roident as "ID" in user facing messages and docs

Browse Source 
The table column that stores this is of type oid, but is actually limited
to uint16 and has a different path for creating new values. Some of
the documentation already referred to it as an ID, so let's standardize
on that.

While at it, most format strings already use %u, so for consintency
change the remaining stragglers using %d.

Per suggestions from Tom Lane and Justin Pryzby
Discussion: https://www.postgresql.org/message-id/3437166.1659620465%40sss.pgh.pa.us
Backpatch to v15
This commit is contained in:
John Naylor
2022-08-18 08:57:13 +07:00
parent 522ae011fa
commit 7cadaac513
2 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
doc/src/sgml/replication-origins.sgml
View File

@ -27,12 +27,12 @@
</para>
<para>
Replication origins have just two properties, a name and an OID. The name,
Replication origins have just two properties, a name and an ID. The name,
which is what should be used to refer to the origin across systems, is
free-form <type>text</type>. It should be used in a way that makes conflicts
between replication origins created by different replication solutions
unlikely; e.g., by prefixing the replication solution's name to it.
The OID is used only to avoid having to store the long version
The ID is used only to avoid having to store the long version
in situations where space efficiency is important. It should never be shared
across systems.
</para>