Re: BUG #8673: Could not open file "pg_multixact/members/xxxx" on slave during hot_standby

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Serge Negodyuck <petr(at)petrovich(dot)kiev(dot)ua>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8673: Could not open file "pg_multixact/members/xxxx" on slave during hot_standby
Date: 2014-06-04 18:10:22
Message-ID: 20140604181022.GQ5146@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Alvaro Herrera wrote:

> I wasn't able to reproduce it that way, but I eventually figured out
> that if I altered altered the plpython function to grab a FOR NO KEY
> UPDATE lock first, insertion would grow the multixact beyond reasonable
> limits; see the attachment. If you then INSERT many tuples in "product"
> in a single transaction, the resulting xmax is a Multixact that has as
> many members as inserts there are, plus one.

Bah. I managed to submit a file with the lock_company() call commented
out in the plpython function. That one doesn't do anything interesting;
you need to uncomment that line.

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Gunnar "Nick" Bluth 2014-06-04 18:14:36 Re: BUG #10527: TRAP when joining local table with view on tds_fdw foreign table
Previous Message Tom Lane 2014-06-04 18:06:07 Re: BUG #10527: TRAP when joining local table with view on tds_fdw foreign table

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-06-04 18:50:39 Re: Proposing pg_hibernate
Previous Message Stephen Frost 2014-06-04 17:57:19 Re: pg_control is missing a field for LOBLKSIZE