Hello, On 2013-12-18 10:24:56 -0800, Dong Ye wrote: > It seems that 0ac5ad5134f2769ccbaefec73844f8504c4d6182 is the culprit > commit.
How long does a run take to verify the problem? Could you retry with the patch attached to http://www.postgresql.org/message-id/20131201114514.gg18...@alap2.anarazel.de ? Based on the theory that it creates many superflous multixacts. > Flat perf profiles of two such runs look like: Those aren't really flat profiles tho ;) > 0ac: > > Samples: 706K of event 'cycles', Event count (approx.): 6690377376522 > > > + 3.82% postgres postgres [.] > GetMultiXactIdMembers Could you expland that one some levels, so we see the callers? Greetings, Andres Freund -- Andres Freund 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
