Re: What is HeapScanDescData.rs_initblock good for? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: What is HeapScanDescData.rs_initblock good for?
Date
Msg-id 20150723193307.GV5596@postgresql.org
Whole thread Raw
In response to Re: What is HeapScanDescData.rs_initblock good for?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Alvaro Herrera <alvherre@2ndquadrant.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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Autonomous Transaction is back
Next
From: Robert Haas
Date:
Subject: Re: [PROPOSAL] VACUUM Progress Checker.