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 1sOof6-001LrL-Ig for pgsql-general@arkaria.postgresql.org; Wed, 03 Jul 2024 01:19:56 +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 1sOof2-005H0u-0a for pgsql-general@arkaria.postgresql.org; Wed, 03 Jul 2024 01:19:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sOof1-005H0m-ME for pgsql-general@lists.postgresql.org; Wed, 03 Jul 2024 01:19:52 +0000 Received: from smtp112.iad3b.emailsrvr.com ([146.20.161.112]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sOoew-0008iZ-DF for pgsql-general@lists.postgresql.org; Wed, 03 Jul 2024 01:19:51 +0000 X-Auth-ID: xof@thebuild.com Received: by smtp23.relay.iad3b.emailsrvr.com (Authenticated sender: xof-AT-thebuild.com) with ESMTPSA id 9E264A00F1; Tue, 2 Jul 2024 21:19:43 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.600.62\)) Subject: Re: Logical replication with temporary tables From: Christophe Pettus In-Reply-To: Date: Tue, 2 Jul 2024 18:19:12 -0700 Cc: pgsql-general@lists.postgresql.org Content-Transfer-Encoding: quoted-printable Message-Id: References: <0FE55AC1-25C2-4B5B-A312-5F8EB4756B4B@thebuild.com> To: Stuart Campbell X-Mailer: Apple Mail (2.3774.600.62) X-Classification-ID: f13346de-e5b5-4fb6-886e-9b42d3e51f24-1-1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Jul 2, 2024, at 18:16, Stuart Campbell = wrote: >=20 > My understanding was that under the hood, AWS uses the logical = replication features that are present in community Postgres. If that's = incorrect then I'm sorry for the off-topic post. Yes, but: The idea of a "degraded" replication is an AWS thing, so it's = hard to say what does or does not cause that state to occur without = access to proprietary AWS code. > Maybe my question can be re-summarised as: do DDL operations on = temporary tables necessarily have to be written to the WAL? Is there a = way to avoid that? Yes, they do (because they involve catalog changes that need to be = WAL-logged), and there is no way of avoiding that in current versions of = PostgreSQL.=