From: | John Naylor <john(dot)naylor(at)postgresql(dot)org> |
---|---|
To: | pgsql-committers(at)lists(dot)postgresql(dot)org |
Subject: | pgsql: Refer to replication origin roident as "ID" in user facing messa |
Date: | 2022-08-18 02:10:14 |
Message-ID: | E1oOUz7-0002oD-6m@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Refer to replication origin roident as "ID" in user facing messages and docs
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
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/c920fe48181d81ce218faa746f8af92c41d03b2e
Modified Files
--------------
doc/src/sgml/replication-origins.sgml | 4 ++--
src/backend/replication/logical/origin.c | 16 ++++++++--------
2 files changed, 10 insertions(+), 10 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | John Naylor | 2022-08-18 02:10:59 | pgsql: Refer to replication origin roident as "ID" in user facing messa |
Previous Message | David Rowley | 2022-08-17 23:33:17 | pgsql: Fix hypothetical problem passing the wrong GROUP BY pathkeys |