Re: Parallel Index Scan vs BTP_DELETED and BTP_HALF_DEAD - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Parallel Index Scan vs BTP_DELETED and BTP_HALF_DEAD
Date
Msg-id CAEepm=2pJAqCrcG-QVLjwSJua33AU7Z7pWVjQGXWse3rMZHG7g@mail.gmail.com
Whole thread Raw
In response to Re: Parallel Index Scan vs BTP_DELETED and BTP_HALF_DEAD  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: Parallel Index Scan vs BTP_DELETED and BTP_HALF_DEAD
List pgsql-hackers
On Wed, Dec 13, 2017 at 3:41 PM, Amit Kapila <amit.kapila16@gmail.com> wrote:
> Good.  I hope that the patch I have posted above is able to resolve
> this problem.  I am asking as you haven't explicitly mentioned that.

I can confirm that your patch fixes the problem for forward scans.
That is, I can see it reaching the BTP_DELETED case via an extra LOG
statement I added, and it worked correctly.  Good.

I don't know how to make it hit the backwards scan case.  I can get a
backward scan in a worker by changing the query to "select count(*)
from (select * from jobs where id + 1 > id order by status desc) ss"
but I suspect that _bt_walk_left() may be hiding deleted pages from us
so the condition may not be reachable with this technique.

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


pgsql-hackers by date:

Previous
From: Haribabu Kommi
Date:
Subject: Re: [HACKERS] Refactor handling of database attributes betweenpg_dump and pg_dumpall
Next
From: Andres Freund
Date:
Subject: pg_ctl on windows can't open postmaster.pid: Permission denied