MIME-Version: 1.0
References: <CAHYXj6eJiX0jQpq4u7xYc1qy3=zBN+sPhGMTJETAF0fdoSyNUA@mail.gmail.com>
In-Reply-To: <CAHYXj6eJiX0jQpq4u7xYc1qy3=zBN+sPhGMTJETAF0fdoSyNUA@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Wed, 28 Aug 2024 08:38:49 -0400
Message-ID: <CAKAnmmJfKZejX0yE8dMHRZiQApq-PO_+aetGCHkkjK3VdOjD3w@mail.gmail.com>
Subject: Re: Ghost data from failed FDW transactions?
To: Jacob Biesinger <jake.biesinger@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="0000000000001b16af0620bda6db"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmmJfKZejX0yE8dMHRZiQApq-PO_%2BaetGCHkkjK3VdOjD3w%40mail.gmail.com>
Precedence: bulk

--0000000000001b16af0620bda6db
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Aug 27, 2024 at 9:03=E2=80=AFPM Jacob Biesinger <jake.biesinger@gma=
il.com>
wrote:

> I'm scratching my head at a few rows in the root DB, where it seems the
> corresponding tenant transaction rolled back, but the root DB transaction
> committed
>
...

> Before I jump into particulars, does this sound like expected behavior?
>

No, it sounds like something is going wrong. Your setup as described should
work to keep both sides in sync.

Through the magic of postgres_fdw, row triggers, and distributed
> transactions,
>

Can you expand on "distributed transactions" here?

Cheers,
Greg

--0000000000001b16af0620bda6db
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Tue, Aug 27, 2024 at 9:03=E2=80=AFPM J=
acob Biesinger &lt;<a href=3D"mailto:jake.biesinger@gmail.com">jake.biesing=
er@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>I&#39;m scratc=
hing my head at a few rows in the root DB, where it seems the corresponding=
 tenant transaction rolled back, but the root DB transaction committed<br><=
/div></div></blockquote><div>...=C2=A0</div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div dir=3D"ltr"><div>Before I jump into particulars, do=
es this sound like expected behavior?</div></div></blockquote><div><br></di=
v><div>No, it sounds like something is going wrong. Your setup as described=
 should work to keep both sides in sync.</div><div><br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid=
 rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Through the magic=
 of postgres_fdw, row triggers, and distributed transactions,</div></div></=
blockquote><div><br></div><div>Can you expand on &quot;distributed transact=
ions&quot; here?</div><div><br></div><div>Cheers,</div><div>Greg</div><div>=
<br></div></div></div>

--0000000000001b16af0620bda6db--