Re: MultiXactMemberControlLock contention on a replica

Поиск
Список
Период
Сортировка
От Laurenz Albe
Тема Re: MultiXactMemberControlLock contention on a replica
Дата
Msg-id d989eeec7ed83ff72cee294d049d21f8ea4347a6.camel@cybertec.at
обсуждение исходный текст
Ответ на Re: MultiXactMemberControlLock contention on a replica  (Christophe Pettus <xof@thebuild.com>)
Ответы Re: MultiXactMemberControlLock contention on a replica  (Christophe Pettus <xof@thebuild.com>)
Список pgsql-general
On Mon, 2021-02-15 at 08:03 -0800, Christophe Pettus wrote:
> On Feb 15, 2021, at 07:47, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
> > So my guess would be that the difference between primary and standby is not that a
> > different number of multixacts are created, but that you need to read them on
> > the standby and not on the primary.
> 
> Why does the secondary need to read them?  Visibility?

Right.  I cannot think of any other reason, given that the standby only
allows reading.  It's just an "xmax", and PostgreSQL needs to read the
multixact to figure out if it can see the row or not.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com




В списке pgsql-general по дате отправления:

Предыдущее
От: Ron
Дата:
Сообщение: ADD FOREIGN KEY fails, but the records exist
Следующее
От: Adrian Klaver
Дата:
Сообщение: Re: ADD FOREIGN KEY fails, but the records exist