Re: logicalrep_message_type throws an error

Поиск
Список
Период
Сортировка
От Alvaro Herrera
Тема Re: logicalrep_message_type throws an error
Дата
Msg-id 20230705105639.lsz7ogusvkukbvs5@alvherre.pgsql
обсуждение исходный текст
Ответ на Re: logicalrep_message_type throws an error  (Amit Kapila <amit.kapila16@gmail.com>)
Ответы Re: logicalrep_message_type throws an error  (Amit Kapila <amit.kapila16@gmail.com>)
Re: logicalrep_message_type throws an error  ("Euler Taveira" <euler@eulerto.com>)
Список pgsql-hackers
On 2023-Jul-05, Amit Kapila wrote:

> I think after returning "???" from logicalrep_message_type(), the
> above is possible when we get the error: "invalid logical replication
> message type "X"" from apply_dispatch(), right? If so, then what about
> the case when we forgot to handle some message in
> logicalrep_message_type() but handled it in apply_dispatch()? Isn't it
> better to return the 'action' from the function
> logicalrep_message_type() for unknown type? That way the information
> could be a bit better and we can easily catch the code bug as well.

Are you suggesting that logicalrep_message_type should include the
numerical value of 'action' in the ??? message? Something like this:

 ERROR:  invalid logical replication message type "X"
 CONTEXT:  processing remote data for replication origin "pg_16638" during message type "??? (123)" in transaction 796,
finishedat 0/16266F8
 

I don't see why not -- seems easy enough, and might help somebody.

-- 
Álvaro Herrera         PostgreSQL Developer  —  https://www.EnterpriseDB.com/
Tom: There seems to be something broken here.
Teodor: I'm in sackcloth and ashes...  Fixed.
                               http://postgr.es/m/482D1632.8010507@sigaev.ru



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Thom Brown
Дата:
Сообщение: Disabling Heap-Only Tuples
Следующее
От: Matthias van de Meent
Дата:
Сообщение: Re: Disabling Heap-Only Tuples