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 1sOofg-001LwI-48 for pgsql-general@arkaria.postgresql.org; Wed, 03 Jul 2024 01:20:32 +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 1sOofe-005MrJ-5e for pgsql-general@arkaria.postgresql.org; Wed, 03 Jul 2024 01:20:30 +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 1sOof9-005IY8-N1 for pgsql-general@lists.postgresql.org; Wed, 03 Jul 2024 01:20:00 +0000 Received: from mail-oa1-x32.google.com ([2001:4860:4864:20::32]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sOof3-0007bN-3F for pgsql-general@lists.postgresql.org; Wed, 03 Jul 2024 01:19:58 +0000 Received: by mail-oa1-x32.google.com with SMTP id 586e51a60fabf-24c0dbd2866so2590831fac.0 for ; Tue, 02 Jul 2024 18:19:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719969592; x=1720574392; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=yKpYEzjGLnhoAfC0YumrfRaqiANE3xzbrtfu6smtv44=; b=Ozcf5ig/nbln4m25kWuXWnDv9RiiqH4mgzRMboS7oORGeY1svfBtnjJAv6Cgn9TAbu ejVJF91ukpzpkVaB1Y/Fa31knAdVR738Hw3UIFMa7gEJD1+zBqezT4VPWjWQS0lVrt7j VfQaN4UwM9zElqQByzgtSBpMNFypgUEvToQrKGL9SPn8RyPPQFG6Ejb3V9xX5LHMQIu6 hVX/g05xsWtMxeKOk0PstrphtL4PWHSuCrA3ZdP7TrGwAcJoREeHrWrp/ZoVwYhz1KOl m5v1BpDPUljO8nM9sgHAgSNnpi8myYJdJKFzuEPFsznOfWfTqkHW2j2nmRzNrZNKxh5r Sq+Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719969592; x=1720574392; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=yKpYEzjGLnhoAfC0YumrfRaqiANE3xzbrtfu6smtv44=; b=E+QcAzHSjsHoTlh3TVWMP5bQzKpy7iCr0qHnZlit9WuXiyO2OR5p8aCto/abujAWl/ QVNGofH1hTmefXbXsuZrW9jxi5CcJRhctRx0+pGQuwls3OBfs9bGkdoAovursxi7whgM HSPW/0dsHh8HpNIdSq99xsSVnVlKoSXxGcVWwC+tg85lAwIDFNfUB1oOQFO7I2RUA2r9 nFLAPk7Lkg6DjhYWx2A8vs8SOb6xrPxcwTMldVLADL+m9QupeSbDDYm4McWN2lbzSrJw CoB9YH5fWmWbziUrY/5/1JunN1jsD/xV8auNo//NVnHqV0XInwF8IdBh/2ZyxqykBdAH 5bPg== X-Forwarded-Encrypted: i=1; AJvYcCWrH66DKxQgoTpzPZCUkE15h5YJFCznefUiLrxwpsa1LNZSWw4CH2A3pZot+Ibmaj5QpbuyifpWwlZpEbhRSjlG4ZSe1jcH3vCvNvW6GgpJjAAF X-Gm-Message-State: AOJu0YzcePM69Wtzhh6aDxtLiMzdO9gZ8Uz1upzQVLUJR1678ahg8rYs US45SPcOUWdA49T83gL8JceFGOz946Lr8mCvXxAG+DwmIilcior1PZ19H91rB83DoNbEcs5bykd 5jqxKTlPaH03QqYWOBoNj6iBT3D8= X-Google-Smtp-Source: AGHT+IGwh3tRD4hPlrPvuZEYHXolO+xmSxQp6xQsdNlOIQZ09XGaIboayfpXvBuUF5YrQDCxOxS8kQEWbTjEY87HpqQ= X-Received: by 2002:a05:6870:96a7:b0:254:a09c:6ddf with SMTP id 586e51a60fabf-25db34d88edmr9503144fac.24.1719969592092; Tue, 02 Jul 2024 18:19:52 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:ac9:6850:0:b0:539:aa10:6c7 with HTTP; Tue, 2 Jul 2024 18:19:51 -0700 (PDT) In-Reply-To: References: <0FE55AC1-25C2-4B5B-A312-5F8EB4756B4B@thebuild.com> From: "David G. Johnston" Date: Tue, 2 Jul 2024 18:19:51 -0700 Message-ID: Subject: Re: Logical replication with temporary tables To: Stuart Campbell Cc: Christophe Pettus , "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="0000000000008fad97061c4da0f7" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008fad97061c4da0f7 Content-Type: text/plain; charset="UTF-8" On Tuesday, July 2, 2024, Stuart Campbell wrote: > This is a question for AWS. Community PostgreSQL doesn't have any of >> these concepts, and this is all proprietary modifications to PostgreSQL by >> Amazon. > > > 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, and no. The tables those commands update are WAL-logged and that status is all-or-nothing. David J. --0000000000008fad97061c4da0f7 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tuesday, July 2, 2024, Stuart Campbell <stuart.campbell@ridewithvia.com> wrote:
This is a question for AWS.=C2=A0 Community PostgreSQL doesn't have any= of these concepts, and this is all proprietary modifications to PostgreSQL= by Amazon.

Maybe my question can be re-sum= marised as: do DDL operations on temporary tables necessarily have to be wr= itten to the WAL? Is there a way to avoid that?


Yes, and no.=C2=A0 The tabl= es those commands update are WAL-logged and that status is all-or-nothing.<= /div>

David J.

=C2=A0
--0000000000008fad97061c4da0f7--