Andres Freund wrote: > On 2014-04-18 11:50:55 -0300, Alvaro Herrera wrote: > > It's a bit painful that HeapTupleHeaderGetUpdateXid allocates memory, > > but to fix that we would have to remove all allocations from > > GetMultiXactIdMembers which doesn't sound feasible. > > I was thinking for a second we could just allocate something during > startup based on max_connections (+ other possible backends), but I > think that won't work because of subtransactions?
Yeah, I don't think the number of members in a multixact is bound. -- Álvaro Herrera http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
