Re: Parallel Index Scan vs BTP_DELETED and BTP_HALF_DEAD

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>
Cc: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Parallel Index Scan vs BTP_DELETED and BTP_HALF_DEAD
Date: 2017-12-13 21:21:59
Message-ID: CA+TgmobHkLty7LL4ADkxf_9xxvqwKtWkbqH+BQ6N9yMCn=4N8A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Dec 13, 2017 at 12:35 AM, Kuntal Ghosh
<kuntalghosh(dot)2007(at)gmail(dot)com> wrote:
> I've also verified the backward scan case with the query provided by
> Thomas. In standby,
> 2. explain analyze select * from t1 where a+1>a order by a desc; and
> the parallel workers hang.
> The patch fixes the issue.

Committed and back-patched to v10.

Sorry, Kuntal, I forgot to credit you in the commit message. :-(

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-12-13 21:35:04 Re: [HACKERS] parallel.c oblivion of worker-startup failures
Previous Message Robert Haas 2017-12-13 21:02:01 Re: explain analyze output with parallel workers - question about meaning of information for explain.depesz.com