Tom Lane wrote:
>
> So, it looks like a solution involves two components: first, being more
> careful to lock system relations appropriately, and second, being sure
> that SI messages are seen soon enough. I think the read-SI-messages-
> at-lock-time code that's already in place for 6.6 will be sufficient for
> the second point, if we are religious about acquiring appropriate locks.
> (BTW, I think that in most cases an appropriate lock on a system table
> will be less strong than AccessExclusiveLock --- Vadim, do you agree?)
ExclusiveLock should be ok.
Vadim
