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: Magnus Hagander <magnus@hagander.net>
Cc: Andres Freund <andres@anarazel.de>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Tomas Vondra <tomas.vondra@2ndquadrant.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2018-03-04T10:03:49Z
Lists: pgsql-hackers
On Sun, Mar 4, 2018 at 10:46 PM, Magnus Hagander <magnus@hagander.net> wrote:
> Um. Have you actually seen the "mail archive app" cut long threads off in
> other cases? Because it's certainly not supposed to do that...

Hi Magnus,

I mean the "flat" thread view:

https://www.postgresql.org/message-id/flat/CAFjFpRfQ8GrQvzp3jA2wnLqrHmaXna-urjm_UY9BqXj=EaDTSA@mail.gmail.com

The final message on that page is not the final message that appears
in my mail client for the thread.  I guessed that might have been cut
off due to some hard-coded limit, but perhaps there is some other
reason (different heuristics for thread following?)

-- 
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.