Re: [BUG]Update Toast data failure in logical replication

Поиск
Список
Период
Сортировка
От Dilip Kumar
Тема Re: [BUG]Update Toast data failure in logical replication
Дата
Msg-id CAFiTN-tJqa3J_s-fSoJEzk55_UGXmU9+8AOBypveiQM_qAwsGQ@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [BUG]Update Toast data failure in logical replication  (Dilip Kumar <dilipbalaut@gmail.com>)
Ответы RE: [BUG]Update Toast data failure in logical replication  ("tanghy.fnst@fujitsu.com" <tanghy.fnst@fujitsu.com>)
Список pgsql-hackers
On Tue, Jun 1, 2021 at 3:39 PM Dilip Kumar <dilipbalaut@gmail.com> wrote:
>
> On Tue, Jun 1, 2021 at 12:29 PM tanghy.fnst@fujitsu.com

> > I noticed that in case1, ExtractReplicaIdentity function returned NULL on HEAD. But after your fix, it didn’t
returnNULL. There is no problem with this case on HEAD, but the patch modified its return value. I’m not sure if it
wouldbring new problems. Have you checked it? 
>
> Good observation, basically, my check says that any field in the tuple
> is toasted then prepare the key tuple, actually, after that, I should
> recheck whether the key field specifically toasted or not and if it is
> not then we can continue returning NULL.  I will fix this in the next
> version.

Attached patch fixes that, I haven't yet added the test case.  Once
someone confirms on the approach then I will add a test case to the
patch.

--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com

Вложения

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

Предыдущее
От: Amit Kapila
Дата:
Сообщение: Re: Decoding speculative insert with toast leaks memory
Следующее
От: "Joel Jacobson"
Дата:
Сообщение: Re: security_definer_search_path GUC