Re: select_parallel test failure: gather sometimes losing tuples (maybe during rescans)?
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Thomas Munro <thomas.munro@enterprisedb.com>
Cc: Magnus Hagander <magnus@hagander.net>, 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-05T16:04:35Z
Lists: pgsql-hackers
Thomas Munro wrote: > 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?) You're thinking of message https://www.postgresql.org/message-id/CAFjFpRfa6_n10cn3vXjN9hdTqneH6A1rfnLXy0PnCP63T2putw@mail.gmail.com but that is not the same thread -- it doesn't have the References or In-Reply-To headers (see "raw"; user/pwd is archives/antispam). Don't know why though -- maybe Gmail trimmed References because it no longer fit in the DKIM signature? Yours had a long one: https://www.postgresql.org/message-id/raw/CAEepm%3D0VCrC-WfzZkq3YSvJXf225rDnp1ypjv%2BrjKO5d0%3DXqFg%40mail.gmail.com -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
shm_mq: Fix detach race condition.
- 42d7074ebb83 11.0 landed
-
shm_mq: Have the receiver set the sender's less frequently.
- 497171d3e2aa 11.0 cited
-
shm_mq: Reduce spinlock usage.
- 34db06ef9a1d 11.0 cited
-
Report an ERROR if a parallel worker fails to start properly.
- 2badb5afb89c 11.0 cited