diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2021-11-10 13:12:58 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2021-11-10 13:12:58 -0500 |
| commit | 886801df4a23d0ee5e2b2119470cbf300242f644 (patch) | |
| tree | fb5c9eaad1ec5b004663fd98114ed6adb192105e /src | |
| parent | 9959a078f2d706d9bbea74891963e6df0a95fedb (diff) | |
| download | postgresql-886801df4a23d0ee5e2b2119470cbf300242f644.tar.gz postgresql-886801df4a23d0ee5e2b2119470cbf300242f644.zip | |
Doc: improve protocol spec for logical replication Type messages.
protocol.sgml documented the layout for Type messages, but completely
dropped the ball otherwise, failing to explain what they are, when
they are sent, or what they're good for. While at it, do a little
copy-editing on the description of Relation messages.
In passing, adjust the comment for apply_handle_type() to make it
clearer that we choose not to do anything when receiving a Type
message, not that we think it has no use whatsoever.
Per question from Stefen Hillman.
Discussion: https://postgr.es/m/CAPgW8pMknK5pup6=T4a_UG=Cz80Rgp=KONqJmTdHfaZb0RvnFg@mail.gmail.com
Diffstat (limited to 'src')
| -rw-r--r-- | src/backend/replication/logical/worker.c | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/src/backend/replication/logical/worker.c b/src/backend/replication/logical/worker.c index 2f448036ea1..90079b63f1d 100644 --- a/src/backend/replication/logical/worker.c +++ b/src/backend/replication/logical/worker.c @@ -559,7 +559,10 @@ apply_handle_relation(StringInfo s) /* * Handle TYPE message. * - * This is now vestigial; we read the info and discard it. + * This implementation pays no attention to TYPE messages; we expect the user + * to have set things up so that the incoming data is acceptable to the input + * functions for the locally subscribed tables. Hence, we just read and + * discard the message. */ static void apply_handle_type(StringInfo s) |