Re: Time delayed LR (WAS Re: logical replication restrictions)
| От | Amit Kapila |
|---|---|
| Тема | Re: Time delayed LR (WAS Re: logical replication restrictions) |
| Дата | |
| Msg-id | CAA4eK1J0cLtAKUg1ezJdHZ1EaSrs-XY0imcNd=16AVS9gSrXxA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Time delayed LR (WAS Re: logical replication restrictions) ("Euler Taveira" <euler@eulerto.com>) |
| Ответы |
RE: Time delayed LR (WAS Re: logical replication restrictions)
|
| Список | pgsql-hackers |
On Tue, Jan 24, 2023 at 5:02 AM Euler Taveira <euler@eulerto.com> wrote: > > > - elog(DEBUG2, "sending feedback (force %d) to recv %X/%X, write %X/%X, flush %X/%X in-delayed: %d", > + elog(DEBUG2, "sending feedback (force %d) to recv %X/%X, write %X/%X, flush %X/%X, apply delay: %s", > force, > LSN_FORMAT_ARGS(recvpos), > LSN_FORMAT_ARGS(writepos), > LSN_FORMAT_ARGS(flushpos), > - in_delayed_apply); > + in_delayed_apply? "yes" : "no"); > > It is better to use a string to represent the yes/no option. > I think it is better to be consistent with the existing force parameter which is also boolean, otherwise, it will look odd. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: