From: | Christophe Pettus <xof(at)thebuild(dot)com> |
---|---|
To: | Stuart Campbell <stuart(dot)campbell(at)ridewithvia(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Logical replication with temporary tables |
Date: | 2024-07-03 01:19:12 |
Message-ID: | B6B249F8-FF16-4846-AA97-97F100C5F606@thebuild.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> On Jul 2, 2024, at 18:16, Stuart Campbell <stuart(dot)campbell(at)ridewithvia(dot)com> 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.
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2024-07-03 01:19:51 | Re: Logical replication with temporary tables |
Previous Message | Stuart Campbell | 2024-07-03 01:16:42 | Re: Logical replication with temporary tables |