Re: Replica Identity check of partition table on subscriber

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: Replica Identity check of partition table on subscriber
Дата
Msg-id CAA4eK1K7rCa0Hfk3+LdtFqEBrr4r6JjsqJPnqJDa6CeDnzwy3g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Replica Identity check of partition table on subscriber  (Amit Langote <amitlangote09@gmail.com>)
Ответы RE: Replica Identity check of partition table on subscriber  ("houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>)
Re: Replica Identity check of partition table on subscriber  (Amit Langote <amitlangote09@gmail.com>)
Список pgsql-hackers
On Fri, Jun 10, 2022 at 2:26 PM Amit Langote <amitlangote09@gmail.com> wrote:
>
> +logicalrep_partmap_invalidate
>
> I wonder why not call this logicalrep_partmap_update() to go with
> logicalrep_relmap_update()?  It seems confusing to have
> logicalrep_partmap_invalidate() right next to
> logicalrep_partmap_invalidate_cb().
>

I am thinking about why we need to update the relmap in this new
function logicalrep_partmap_invalidate()? I think it may be better to
do it in logicalrep_partition_open() when actually required,
otherwise, we end up doing a lot of work that may not be of use unless
the corresponding partition is accessed. Also, it seems awkward to me
that we do the same thing in this new function
logicalrep_partmap_invalidate() and then also in
logicalrep_partition_open() under different conditions.

One more point about the 0001, it doesn't seem to have a test that
validates logicalrep_partmap_invalidate_cb() functionality. I think
for that we need to Alter the local table (table on the subscriber
side). Can we try to write a test for it?

-- 
With Regards,
Amit Kapila.



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

Предыдущее
От: David Zhang
Дата:
Сообщение: Re: Non-replayable WAL records through overflows and >MaxAllocSize lengths
Следующее
От: Thomas Munro
Дата:
Сообщение: Re: Collation version tracking for macOS