Re: select_parallel test failure: gather sometimes losing tuples (maybe during rescans)?

Thomas Munro <thomas.munro@enterprisedb.com>

From: Thomas Munro <thomas.munro@enterprisedb.com>
To: Andres Freund <andres@anarazel.de>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2018-03-04T02:51:07Z
Lists: pgsql-hackers
On Sun, Mar 4, 2018 at 3:48 PM, Thomas Munro
<thomas.munro@enterprisedb.com> wrote:
> I've seen it several times on Travis CI.  (So I would normally have
> been able to tell you about this problem before the was committed,
> except that the email thread was too long and the mail archive app
> cuts long threads off!)

(Correction.  It wasn't too long.  That was something else.  In this
case the Commitfest entry had two threads registered and my bot is too
stupid to find the interesting one.)

-- 
Thomas Munro
http://www.enterprisedb.com


Commits

  1. shm_mq: Fix detach race condition.

  2. shm_mq: Have the receiver set the sender's less frequently.

  3. shm_mq: Reduce spinlock usage.

  4. Report an ERROR if a parallel worker fails to start properly.