Re: What is HeapScanDescData.rs_initblock good for?

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: What is HeapScanDescData.rs_initblock good for?
Date: 2015-07-23 19:33:07
Message-ID: 20150723193307.GV5596@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> > Tom Lane wrote:
> >> I'm inclined to let it call heap_setscanlimits only if not allow_sync.
>
> > It is possible for a partial range scan to join an existing herd of
> > scans that happens to be processing that part of the table, in which
> > case this wouldn't be sufficient. However, two considerations: 1) range
> > scans, at least for BRIN, aren't normally large enough for synscans to
> > matter all that much; and 2) it would require additional code. So I'm
> > inclined to do it as you suggest, which is simplest.
>
> I already did that, but feel free to whack it further if you're so
> inclined.

Nah, I just failed to see your commit.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2015-07-23 19:35:13 Speakers Wanted for pgDay Cuba
Previous Message Qingqing Zhou 2015-07-23 19:27:02 Re: Planner debug views