Re: Ghost data from failed FDW transactions? - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: Ghost data from failed FDW transactions?
Date
Msg-id CAKAnmmJfKZejX0yE8dMHRZiQApq-PO_+aetGCHkkjK3VdOjD3w@mail.gmail.com
Whole thread Raw
In response to Ghost data from failed FDW transactions?  (Jacob Biesinger <jake.biesinger@gmail.com>)
Responses Re: Ghost data from failed FDW transactions?
List pgsql-general
On Tue, Aug 27, 2024 at 9:03 PM Jacob Biesinger <jake.biesinger@gmail.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

pgsql-general by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: Pgbackrest specifying the default DB necessary/correct way ?
Next
From: KK CHN
Date:
Subject: Re: Pgbackrest specifying the default DB necessary/correct way ?