Re: More race conditions in logical replication

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>

To: Alvaro Herrera <alvherre@2ndquadrant.com>

Cc: Petr Jelinek <petr.jelinek@2ndquadrant.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Peter Eisentraut <peter.eisentraut@2ndquadrant.com>

Date: 2017-08-08T00:36:51Z

Lists: pgsql-hackers

On Mon, Aug 7, 2017 at 8:14 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> BTW, I noticed that the PG_WAIT_LOCK value that we're using for wait
> event here (and in the replication slot case) is bogus.  We probably
> need something new here.

Yeah, if you're adding a new wait point, you should add document a new
constant in the appropriate section, probably something under
PG_WAIT_IPC in this case.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

Commits

Fix vertical spanning in table "wait_event Description".
- e88928c50dfe 10.0 landed
Fix replication origin-related race conditions
- b2c95a3798ff 10.0 landed
Fix inadequacies in recently added wait events
- 030273b7ea46 10.0 landed
Fix race conditions in replication slot operations
- 9915de6c1cb2 10.0 landed