Re: What is HeapScanDescData.rs_initblock good for?

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

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2015-07-23 18:15:58 Re: A little RLS oversight?
Previous Message Florent Guiliani 2015-07-23 18:08:39 Re: Retrieve the snapshot's LSN