Re: refresh materialized view concurrently

Kevin Grittner <kgrittn@ymail.com> writes:
> OK.� I had seen that no locks were held after the insert and wasn't
> aware that we acquired and then released them for each insert
> within a transaction.� On the other hand, we acquire locks on all
> indexes even for a HOT UPDATE which uses a seqscan, and hold those
> until end of transaction.� Is there a reason for that?

Sounds dubious to me; although in the HOT code it might be that there's
no convenient place to release the index locks.
        regards, tom lane