| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: MultiXactMemberControlLock contention on a replica |
| Date: | 2021-02-15 16:15:41 |
| Message-ID: | d989eeec7ed83ff72cee294d049d21f8ea4347a6.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Mon, 2021-02-15 at 08:03 -0800, Christophe Pettus wrote:
> On Feb 15, 2021, at 07:47, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2021-02-15 16:17:55 | Re: ADD FOREIGN KEY fails, but the records exist |
| Previous Message | Ron | 2021-02-15 16:12:30 | ADD FOREIGN KEY fails, but the records exist |