diff options
| author | Amit Kapila <akapila@postgresql.org> | 2020-11-02 08:18:18 +0530 |
|---|---|---|
| committer | Amit Kapila <akapila@postgresql.org> | 2020-11-02 08:18:18 +0530 |
| commit | 644f0d7cc9c2cb270746f2024c706554e0fbec82 (patch) | |
| tree | f92a2763d4fcb5e17a1706437bc264445cdad750 /src/backend/executor/nodeLimit.c | |
| parent | a929e17e5a8c9b751b66002c8a89fdebdacfe194 (diff) | |
| download | postgresql-644f0d7cc9c2cb270746f2024c706554e0fbec82.tar.gz postgresql-644f0d7cc9c2cb270746f2024c706554e0fbec82.zip | |
Use Enum for top level logical replication message types.
Logical replication protocol uses a single byte character to identify a
message type in logical replication protocol. The code uses string
literals for the same. Use Enum so that
1. All the string literals used can be found at a single place. This
makes it easy to add more types without the risk of conflicts.
2. It's easy to locate the code handling a given message type.
3. When used with switch statements, it is easy to identify the missing
cases using -Wswitch.
Author: Ashutosh Bapat
Reviewed-by: Kyotaro Horiguchi, Andres Freund, Peter Smith and Amit Kapila
Discussion: https://postgr.es/m/CAExHW5uPzQ7L0oAd_ENyvaiYMOPgkrAoJpE+ZY5-obdcVT6NPg@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeLimit.c')
0 files changed, 0 insertions, 0 deletions