public inbox for [email protected]
help / color / mirror / Atom feedFrom: Greg Sabino Mullane <[email protected]>
To: Jacob Biesinger <[email protected]>
Cc: [email protected]
Subject: Re: Ghost data from failed FDW transactions?
Date: Wed, 28 Aug 2024 08:38:49 -0400
Message-ID: <CAKAnmmJfKZejX0yE8dMHRZiQApq-PO_+aetGCHkkjK3VdOjD3w@mail.gmail.com> (raw)
In-Reply-To: <CAHYXj6eJiX0jQpq4u7xYc1qy3=zBN+sPhGMTJETAF0fdoSyNUA@mail.gmail.com>
References: <CAHYXj6eJiX0jQpq4u7xYc1qy3=zBN+sPhGMTJETAF0fdoSyNUA@mail.gmail.com>
On Tue, Aug 27, 2024 at 9:03 PM Jacob Biesinger <[email protected]>
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
view thread (6+ messages) latest in thread
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: Ghost data from failed FDW transactions?
In-Reply-To: <CAKAnmmJfKZejX0yE8dMHRZiQApq-PO_+aetGCHkkjK3VdOjD3w@mail.gmail.com>
* 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