Re: pg_upgrade and publication/subscription problem

Поиск
Список
Период
Сортировка
От Marcos Pegoraro
Тема Re: pg_upgrade and publication/subscription problem
Дата
Msg-id CAB-JLwbZqMkj+9kKoBXcuQ01GvHHLjWv9o=UbbMSthYNHf7b6A@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pg_upgrade and publication/subscription problem  (Amit Kapila <amit.kapila16@gmail.com>)
Список pgsql-hackers
Sorry, I didn´t explain exactly what I was doing, I just wrote "This replication is a auditing database" on my second email.

Atenciosamente, 




Em seg., 29 de nov. de 2021 às 09:20, Amit Kapila <amit.kapila16@gmail.com> escreveu:
On Mon, Nov 29, 2021 at 5:04 PM Marcos Pegoraro <marcos@f10.com.br> wrote:
>>
>> On thinking about this point again, it is not clear to me why that
>> would matter for this particular use case? Basically, when you create
>> a new subscription, it should copy the entire existing data from the
>> table directly and then will decode changes from WAL. So, I think in
>> your case all the changes between pg_upgrade and now should be
>> directly copied from tables, so probably older WAL won't be required.
>
>
> Maybe you did not understand
>

Yeah, because some information like trigger functions was not there in
your previous emails.

--
With Regards,
Amit Kapila.

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

Предыдущее
От: Robert Haas
Дата:
Сообщение: Re: Rationalizing declarations of src/common/ variables
Следующее
От: Guillaume Lelarge
Дата:
Сообщение: Lots of memory allocated when reassigning Large Objects