[HACKERS] tablesync patch broke the assumption that logical rep depends on? - Mailing list pgsql-hackers

From Fujii Masao
Subject [HACKERS] tablesync patch broke the assumption that logical rep depends on?
Date
Msg-id CAHGQGwGhhJyNDEb+GDbJ2iHQvyOqcdgqoH9wqvLt7VAGAnE3WA@mail.gmail.com
Whole thread Raw
Responses Re: [HACKERS] tablesync patch broke the assumption that logical rep depends on?  (Noah Misch <noah@leadboat.com>)
Re: [HACKERS] tablesync patch broke the assumption that logical repdepends on?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Re: [HACKERS] tablesync patch broke the assumption that logical repdepends on?  (Steve Singer <steve@ssinger.info>)
List pgsql-hackers
Hi,
        src/backend/replication/logical/launcher.c        * Worker started and attached to our shmem. This check is
safe       * because only launcher ever starts the workers, so nobody can steal        * the worker slot.
 

The tablesync patch enabled even worker to start another worker.
So the above assumption is not valid for now.

This issue seems to cause the corner case where the launcher picks up
the same worker slot that previously-started worker has already picked
up to start another worker.

Regards,

-- 
Fujii Masao



pgsql-hackers by date:

Previous
From: ilmari@ilmari.org (Dagfinn Ilmari Mannsåker)
Date:
Subject: Re: [HACKERS] Compiler warning in costsize.c
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] logical replication and SIGHUP