Re: [BUG]Invalidate relcache when setting REPLICA IDENTITY

Поиск
Список
Период
Сортировка
От Euler Taveira
Тема Re: [BUG]Invalidate relcache when setting REPLICA IDENTITY
Дата
Msg-id bcf89ed4-b632-482f-8f1b-0e4f06723ef7@www.fastmail.com
обсуждение исходный текст
Ответ на RE: [BUG]Invalidate relcache when setting REPLICA IDENTITY  ("houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>)
Ответы Re: [BUG]Invalidate relcache when setting REPLICA IDENTITY  (Amit Kapila <amit.kapila16@gmail.com>)
Список pgsql-hackers
On Fri, Nov 12, 2021, at 3:10 AM, houzj.fnst@fujitsu.com wrote:
On Fri, Nov 12, 2021 1:33 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> On Fri, Nov 12, 2021 at 10:50 AM Amit Kapila <amit.kapila16@gmail.com> wrote:
> > But won't that generate invalidation for the rel twice in the case
> > (change Replica Identity from Nothing to some index) you mentioned in
> > the previous email?
> >

> Oh, I see the point. I think this is okay because
> AddRelcacheInvalidationMessage doesn't allow to add duplicate rel
> invalidation. If that is the case I wonder why not simply register
> invalidation without any check in the for loop as was the case with
> Tang's original patch?

OK, I also think the code in Tang's original patch is fine.
Attach the patch which register invalidation without any check in the for loop.
WFM.


--
Euler Taveira

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

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Is heap_page_prune() stats collector accounting wrong?
Следующее
От: Peter Geoghegan
Дата:
Сообщение: Re: Is heap_page_prune() stats collector accounting wrong?