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 1sOocK-001LcD-3h for pgsql-general@arkaria.postgresql.org; Wed, 03 Jul 2024 01:17:04 +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 1sOocI-005Dom-3J for pgsql-general@arkaria.postgresql.org; Wed, 03 Jul 2024 01:17:02 +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 1sOocH-005DoR-NN for pgsql-general@lists.postgresql.org; Wed, 03 Jul 2024 01:17:02 +0000 Received: from mail-lf1-x12a.google.com ([2a00:1450:4864:20::12a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sOocC-0007Ye-6c for pgsql-general@lists.postgresql.org; Wed, 03 Jul 2024 01:16:58 +0000 Received: by mail-lf1-x12a.google.com with SMTP id 2adb3069b0e04-5295e488248so6278295e87.2 for ; Tue, 02 Jul 2024 18:16:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ridewithvia.com; s=google; t=1719969413; x=1720574213; 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=bDk7rr1BynM2VM4gX+wsuOCPbEVhPWIry5Crd5JfIkk=; b=fLB+GrmfCCeZ9jYXZ1H3gDTsnGMOo9rO39C39DnGWgCMwbE+2kASBVhmuUWc3BL+1g NuQMQBFiSmZWXifJB4Khr7tDo21DF38nwMEqSbY5G76yR1DrrTFUrhs0AsaLlhO2yRfo 4C1ChIqF5+fnhprnq9ZLgneD77NW+Dsd445yg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719969413; x=1720574213; 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=bDk7rr1BynM2VM4gX+wsuOCPbEVhPWIry5Crd5JfIkk=; b=PK+Vt5ounwMZIDF3WVQFg7hkPtTWaBW2PghtYge4Xqbe6rfN9DXK3SjOpb+oYH4YA/ ySC/6Wv0q0/AoeLBWaJhT/SVZYknVOW/52B3jrpol9FI0H0ht93fT6w//mcMXP/CByxO 7y4Vfm2K1tdppuygslJ8ypW/emkMnva3oy2Bacx93oUR6ZRj2mSkOyIMcm0FiBiLldSW SlHUvjH1haTXjwTNMl3Lzl3zHEJKA8HNYL/k6KpIxeA1zWelDzCylRVWQFcZWNkkr5uY BC/El4VP+OQRpP2UZ1sHfef9A8ePTNSBBDoAmTEfLhC3X0VtSik4UY6ukTKnH93dPtAt IKsw== X-Gm-Message-State: AOJu0YyE6zJhyqph6YQ8p+ddwK2VWgt3/r47Qo6l+tb0ybPhK2sj3Tsx 1kzBeXjL6wUkbv7XWI/mcpelSFgGmpGawrmVDRhVeo742NaUJXAnDcnF7Fto0GYnrsOf/a+amUO i32FQ9cPgaiAUnz59zzehQboOWQUPQUEysrATVLT2JxcnDil//eIpDl51+jgj3U9ZU++ptN/ocr pjWkWYe2WA1ikZuUYJydX5hXCH5P0MkBBGiifvTNMlKEK3rdkN X-Google-Smtp-Source: AGHT+IHM7i8bfUT8ra2NdXsS4W/D+uxosAhZ8reAyyDCRCZSEsPK7r82K+bH4ducASc2fUmFTPflpRSaAwWNyuMpdao= X-Received: by 2002:a05:6512:3d8e:b0:52c:9421:2739 with SMTP id 2adb3069b0e04-52e8264dff6mr7289549e87.9.1719969413472; Tue, 02 Jul 2024 18:16:53 -0700 (PDT) MIME-Version: 1.0 References: <0FE55AC1-25C2-4B5B-A312-5F8EB4756B4B@thebuild.com> In-Reply-To: <0FE55AC1-25C2-4B5B-A312-5F8EB4756B4B@thebuild.com> From: Stuart Campbell Date: Wed, 3 Jul 2024 11:16:42 +1000 Message-ID: Subject: Re: Logical replication with temporary tables To: Christophe Pettus Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000eaac1e061c4d95ff" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000eaac1e061c4d95ff Content-Type: text/plain; charset="UTF-8" > > 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. 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. 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? -- This communication and any attachments may contain confidential information and are intended to be viewed only by the intended recipients. If you have received this message in error, please notify the sender immediately by replying to the original message and then delete all copies of the email from your systems. --000000000000eaac1e061c4d95ff Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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.

My understanding was that under= the hood, AWS uses the logical replication features that are present in co= mmunity Postgres. If that's incorrect then I'm sorry for the off-to= pic post.

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

This communication and any attachments may contain confidential inform= ation and are intended to be viewed only by the intended recipients. If you= have received this message in error, please notify the sender immediately = by replying to the original message and then delete all copies of the email= from your systems.


--000000000000eaac1e061c4d95ff--