Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rvE6s-00AaQ4-2h for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Apr 2024 10:26:18 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rvE6p-00CRPV-J7 for pgsql-hackers@arkaria.postgresql.org; Fri, 12 Apr 2024 10:26:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rvE6p-00CRPN-9u for pgsql-hackers@lists.postgresql.org; Fri, 12 Apr 2024 10:26:15 +0000 Received: from mail-oa1-x2b.google.com ([2001:4860:4864:20::2b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rvE6k-002URQ-K8 for pgsql-hackers@lists.postgresql.org; Fri, 12 Apr 2024 10:26:14 +0000 Received: by mail-oa1-x2b.google.com with SMTP id 586e51a60fabf-23335730db1so419610fac.2 for ; Fri, 12 Apr 2024 03:26:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712917569; x=1713522369; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FnEBGo6zZ3pgMjLbyaM8nRRuge8a7b5D6uM9RoDknSE=; b=kWbMG1HV90X9JJ6faHKiMFpkXvaNub14QhDv2fcC5dnoN1ycGNqgeocnl3DCwqPc/0 cyD3C4yvdjfIQ/l6af1lwWriy8VjXTxtr+U4JfrJmavwZ+1D1DS64qBxvW49uflh3Efz M7UkGco3KAHCpMD3uWmT5MkWwA8ECJ1Mh0uAyuXVV0mwITOBB/ZK07YY4EB7Wzb3HyXn JAOA9SorVIKYCNJIqjbl3xscaaidcV0znJSDRlZQmn4qkbzkyJVZp68mSQxPQxalDl5w yJXBD05+r7XwuV9TEWMVZUCg6M69KR8PT+SkNUhZ4pxmlkKEGP2nddY7iW5CVaJt7kbB 7PhA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712917569; x=1713522369; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FnEBGo6zZ3pgMjLbyaM8nRRuge8a7b5D6uM9RoDknSE=; b=XNEwb66+iqX54PKkexPsy5cL9wjOXUaqPRMvv8dKfDuNMp6vmLK/J4j1BJdNje3yHs PQ8PCUlVarG8PiHKEL24dTWbcpAJSNHcL5VW1fxpeDKY4QdYKNg3ulYqsOXDTIa+S42p 0sJVGR9LqXpMAwdUfr6JKopZqUH8qA7YG9HEZ0sJHFUF8smu4AYewCBIhWyQaC+GSpOO vIYFFLHiQvbblAKnCa77aN/irvVlRiPfG19cHzKyQWHLktLk6+6DWESDfZkvBjWLCuMD mWe6uCegan4d6VR79eS0Mm+XLsp9kLa0DyzTULMoIw756rqg/ytbseINDRcT5PASu2BJ p5zQ== X-Gm-Message-State: AOJu0YxWmF8bM7LoP9drZL2W5p/w+TwMexB4Ivz5rNJntDqdMi5d6Pid a3FP6Zw5/Z00n2FkKCyCoTREWn3v2WKO0X9E2UluFV8+3MrCu9WKNY0kpXYxhiPdxKbEhsipduC cOCnfDlEFAFe/JzIChjeotmZCFWo= X-Google-Smtp-Source: AGHT+IF7JmC5qmGgSzTJ3XNN/DMOFl5BTV/uZsONKkK9KiPyuzap7Rk74FDc4rPRssbS9SkSzWJ4tCE+eQOy7GCkCsE= X-Received: by 2002:a05:6870:2484:b0:22e:ae2f:7a9c with SMTP id s4-20020a056870248400b0022eae2f7a9cmr1999159oaq.56.1712917569473; Fri, 12 Apr 2024 03:26:09 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Amit Kapila Date: Fri, 12 Apr 2024 15:55:57 +0530 Message-ID: Subject: Re: pg_upgrde failed : logical replication : alter_subscription_add_log To: Perumal Raj Cc: PostgreSQL Hackers Content-Type: multipart/alternative; boundary="00000000000042145c0615e3b398" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000042145c0615e3b398 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Note - Please keep pgsql-hackers in CC while responding. On Fri, Apr 12, 2024 at 10:44=E2=80=AFAM Perumal Raj = wrote: > Thanks Amit for the update, > > Documentation says : https://www.postgresql.org/docs/15/upgrading.html > > 19.6.3. Upgrading Data via Replication > > It is also possible to use logical replication methods to create a standb= y > server with the updated version of PostgreSQL. This is possible because > logical replication supports replication between different major versions > of PostgreSQL. The standby can be on the same computer or a different > computer. Once it has synced up with the primary server (running the olde= r > version of PostgreSQL), you can switch primaries and make the standby the > primary and shut down the older database instance. Such a switch-over > results in only several seconds of downtime for an upgrade. > > This method of upgrading can be performed using the built-in logical > replication facilities as well as using external logical replication > systems such as pglogical, Slony, Londiste, and Bucardo. > > What is "built-in logical replication" ? > See docs at [1]. [1] - https://www.postgresql.org/docs/devel/logical-replication.html -- With Regards, Amit Kapila --00000000000042145c0615e3b398 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Note - Please keep pgsql-hackers in CC wh= ile responding.

On Fri, Apr 12, 2024 at 10:44=E2=80=AFAM Perumal Raj <perucinci@gmail.com> wrote:
=
Th= anks Amit for the update,


=

19= .6.3.=C2=A0Upgrading Data via Replication

It is also po= ssible to use logical replication methods to create a standby server with t= he updated version of=C2=A0PostgreSQL= . This is possible because logical replication supports replication = between different major versions of=C2=A0PostgreSQL. The standby can be on the same computer or a differe= nt computer. Once it has synced up with the primary server (running the old= er version of=C2=A0PostgreSQL)= , you can switch primaries and make the standby the primary and shut down t= he older database instance. Such a switch-over results in only several seco= nds of downtime for an upgrade.

This method of upgrading can be performed = using the built-in logical replication facilities as well as using external= logical replication systems such as=C2=A0pglogical,=C2=A0Slony,=C2=A0Londiste, and=C2=A0<= span style=3D"box-sizing:border-box">Bucardo.

What is "built-i= n logical replication" ?=C2=A0

Amit Kapila
--00000000000042145c0615e3b398--