public inbox for [email protected]
help / color / mirror / Atom feedFrom: Christophe Pettus <[email protected]>
To: Stuart Campbell <[email protected]>
Cc: [email protected]
Subject: Re: Logical replication with temporary tables
Date: Tue, 2 Jul 2024 18:19:12 -0700
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAAZ6Snxs+6si7gP5yrLNeGAzFgf9_mL1Di+C-_kOAW+96vs+xg@mail.gmail.com>
References: <CAAZ6SnzRU=qo2nedBa6ESOHfV=WaRJk+UW5DUrxkVMu6Gjpwng@mail.gmail.com>
<[email protected]>
<CAAZ6Snxs+6si7gP5yrLNeGAzFgf9_mL1Di+C-_kOAW+96vs+xg@mail.gmail.com>
> On Jul 2, 2024, at 18:16, Stuart Campbell <[email protected]> wrote:
>
> 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.
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Logical replication with temporary tables
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox