Horton
Menu

Re: Perform streaming logical transactions by background workers and parallel apply

Amit Kapila <amit.kapila16@gmail.com>

View thread
From: Amit Kapila <amit.kapila16@gmail.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: "houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>, "shiy.fnst@fujitsu.com" <shiy.fnst@fujitsu.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2022-05-03T04:15:14Z
Lists: pgsql-hackers 
On Mon, May 2, 2022 at 5:06 PM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
>
> On Mon, May 2, 2022 at 6:09 PM Amit Kapila <amit.kapila16@gmail.com> wrote:
> >
> > On Mon, May 2, 2022 at 11:47 AM Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> > >
> > >
> > > Are you planning to support "Transaction dependency" Amit mentioned in
> > > his first mail in this patch? IIUC since the background apply worker
> > > applies the streamed changes as soon as receiving them from the main
> > > apply worker, a conflict that doesn't happen in the current streaming
> > > logical replication could happen.
> > >
> >
> > This patch seems to be waiting for stream_stop to finish, so I don't
> > see how the issues related to "Transaction dependency" can arise? What
> > type of conflict/issues you have in mind?
>
> Suppose we set both publisher and subscriber:
>
> On publisher:
> create table test (i int);
> insert into test values (0);
> create publication test_pub for table test;
>
> On subscriber:
> create table test (i int primary key);
> create subscription test_sub connection '...' publication test_pub; --
> value 0 is replicated via initial sync
>
> Now, both 'test' tables have value 0.
>
> And suppose two concurrent transactions are executed on the publisher
> in following order:
>
> TX-1:
> begin;
> insert into test select generate_series(0, 10000); -- changes will be streamed;
>
>     TX-2:
>     begin;
>     delete from test where c = 0;
>     commit;
>
> TX-1:
> commit;
>
> With the current streaming logical replication, these changes will be
> applied successfully since the deletion is applied before the
> (streamed) insertion. Whereas with the apply bgworker, it fails due to
> an unique constraint violation since the insertion is applied first.
> I've confirmed that it happens with v5 patch.
>

Good point but I am not completely sure if doing transaction
dependency tracking for such cases is really worth it. I feel for such
concurrent cases users can anyway now also get conflicts, it is just a
matter of timing. One more thing to check transaction dependency, we
might need to spill the data for streaming transactions in which case
we might lose all the benefits of doing it via a background worker. Do
we see any simple way to avoid this?


-- 
With Regards,
Amit Kapila.

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix invalid memory access during the shutdown of the parallel apply worker.

  2. Fix assertion failure in apply worker.

  3. Use elog to report unexpected action in handle_streamed_transaction().

  4. Use appropriate wait event when sending data in the apply worker.

  5. Allow the logical_replication_mode to be used on the subscriber.

  6. Rename GUC logical_decoding_mode to logical_replication_mode.

  7. Display the leader apply worker's PID for parallel apply workers.

  8. Improve the code to decide and process the apply action.

  9. Document the newly added wait events added by commit 216a784829.

  10. Perform apply of large transactions by parallel workers.

  11. Wake up a subscription's replication worker processes after DDL.

  12. Add copyright notices to meson files

  13. Better document logical replication parameters

  14. Add a common function to generate the origin name.

  15. Harmonize parameter names in storage and AM code.

  16. Avoid using list_length() to test for empty list.

  17. Improve two comments related to a boolean DefElem's value

  18. Fix partition table's REPLICA IDENTITY checking on the subscriber.

  19. Fix data inconsistency between publisher and subscriber.

  20. Fix cache look-up failures while applying changes in logical replication.