Re: pg_upgrade and logical replication
От | Amit Kapila |
---|---|
Тема | Re: pg_upgrade and logical replication |
Дата | |
Msg-id | CAA4eK1K4uX=g5tgkqhZsmmUKk9NtsM6YTQwA9NFrH-Wr76w1uA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pg_upgrade and logical replication (vignesh C <vignesh21@gmail.com>) |
Ответы |
Re: pg_upgrade and logical replication
Re: pg_upgrade and logical replication |
Список | pgsql-hackers |
On Fri, Nov 10, 2023 at 7:26 PM vignesh C <vignesh21@gmail.com> wrote: > > Thanks for the comments, the attached v13 version patch has the > changes for the same. > + + ReplicationOriginNameForLogicalRep(subid, InvalidOid, originname, sizeof(originname)); + originid = replorigin_by_name(originname, false); + replorigin_advance(originid, sublsn, InvalidXLogRecPtr, + false /* backward */ , + false /* WAL log */ ); This seems to update the origin state only in memory. Is it sufficient to use this here? Anyway, I think using this requires us to first acquire RowExclusiveLock on pg_replication_origin something the patch is doing for some other system table. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: