Re: foreign key locks, 2nd attempt
| От | Simon Riggs |
|---|---|
| Тема | Re: foreign key locks, 2nd attempt |
| Дата | |
| Msg-id | CA+U5nM+gb_vBSCcWUwGxEtypV9v7h69zaA_3i1zZn0SrR5z8XQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: foreign key locks, 2nd attempt (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: foreign key locks, 2nd attempt
|
| Список | pgsql-hackers |
On Wed, Mar 14, 2012 at 5:23 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>> You still have HEAP_XMAX_{INVALID,COMMITTED} to reduce the pressure on mxid
>> lookups, so I think something more sophisticated is needed to exercise that
>> cost. Not sure what.
>
> I don't think HEAP_XMAX_COMMITTED is much help, because committed !=
> all-visible.
So because committed does not equal all visible there will be
additional lookups on mxids? That's complete rubbish.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
В списке pgsql-hackers по дате отправления: