Re: pg_upgrade and logical replication
| От | Amit Kapila | 
|---|---|
| Тема | Re: pg_upgrade and logical replication | 
| Дата | |
| Msg-id | CAA4eK1KW36nzcySUn32+5v5KqcksMw6ZrS3PTMyo9oL_B8nw6Q@mail.gmail.com обсуждение исходный текст  | 
		
| Ответ на | Re: pg_upgrade and logical replication (Amit Kapila <amit.kapila16@gmail.com>) | 
| Ответы | 
                	
            		Re: pg_upgrade and logical replication
            		
            		 | 
		
| Список | pgsql-hackers | 
On Mon, Nov 13, 2023 at 5:01 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > 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? > I think it is probably getting ensured by clean shutdown (shutdown_checkpoint) which happens on the new cluster after calling this function. We can probably try to add a comment for it. BTW, we also need to ensure that max_replication_slots is configured to a value higher than origins we are planning to create on the new cluster. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: