Re: RFC: logical publication via inheritance root?

Поиск
Список
Период
Сортировка
От Amit Kapila
Тема Re: RFC: logical publication via inheritance root?
Дата
Msg-id CAA4eK1+aB-PpY2c4ufE=t6gO4UyP-rimheq9D3BfyJpDfuBAWw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: RFC: logical publication via inheritance root?  (Jacob Champion <jchampion@timescale.com>)
Ответы Re: RFC: logical publication via inheritance root?  (Jacob Champion <jchampion@timescale.com>)
Список pgsql-hackers
On Tue, Jun 20, 2023 at 10:39 PM Jacob Champion <jchampion@timescale.com> wrote:
>
> On Fri, Jun 16, 2023 at 9:24 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
>
> > The other idea that came across my mind was to provide some schema
> > mapping kind of feature on subscribers where we could route the tuples
> > from table X to table Y provided they have the same or compatible
> > schema. I don't know if this is feasible or how generally it will be
> > useful and whether any other DB (replication solution) provides such a
> > feature but I guess something like that would have helped your use
> > case.
>
> Yes, that may have also worked. Making it a subscriber-side feature
> requires tight coupling between the two peers, though. (For the
> timescaledb case, how does the subscriber know which new partitions
> belong to which root?
>

Yeah, the subscriber can't figure that out automatically. Users need
to provide the mapping manually.

--
With Regards,
Amit Kapila.



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

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: [BUG] recovery of prepared transactions during promotion can fail
Следующее
От: Nazir Bilal Yavuz
Дата:
Сообщение: bgwriter doesn't flush WAL stats