Re: More protocol.h replacements this time into walsender.c
От | Jacob Champion |
---|---|
Тема | Re: More protocol.h replacements this time into walsender.c |
Дата | |
Msg-id | CAOYmi+mTZcww9k2o+Stc9QSD-cUPC4t_c0Nn_TFQA2c443UdkA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: More protocol.h replacements this time into walsender.c (Dave Cramer <davecramer@gmail.com>) |
Ответы |
Re: More protocol.h replacements this time into walsender.c
|
Список | pgsql-hackers |
On Thu, Jul 24, 2025 at 12:04 PM Dave Cramer <davecramer@gmail.com> wrote: > Patch attached +/* Replication Protocol sent by the primary */ + +#define PqMsg_XlogData 'w' +#define PqMsg_PrimaryKeepAlive 'k' +#define PqMsg_PrimaryStatusUpdate 's' + + +/* Replication Protocol sent by the standby */ + +#define PqMsg_StandbyStatus 'r' +#define PqMsg_HotStandbyFeedback 'h' +#define PqMsg_RequestPrimaryStatus 'p' Since these are part of the replication subprotocol (i.e. tunneled, via CopyData) rather than the top-level wire protocol, do they deserve their own prefix? PqReplMsg_* maybe? +/* These are the codes sent by the frontend and backend. */ + +#define PqMsg_PasswordMessage 'p' + +/* These are the codes sent by the frontend and backend. */ Is this change intended? --Jacob
В списке pgsql-hackers по дате отправления: