Re: Block level concurrency during recovery

> * For GIN indexes, we appear to not hold a Cleanup lock during
> vacuuming, except on root page. That stops new scans from starting, but
> it doesn't prevent progress of concurrent scans. Doesn't look correct to
> me... so not sure what strength lock to acquire in each case. Probably
Why do you think so?

> need to differentiate between WAL record types so we can tell which to
> acquire CleanupLock for and which not.
>
> * GIST doesn't use CleaupLocks at all. So I'm very unclear here.
Scan process does not hold any pointer on page now, insertion process holds but
it tracks changes of page by looking at LSN of page.

--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/