Re: synchronous commit vs. hint bits
От | Tom Lane |
---|---|
Тема | Re: synchronous commit vs. hint bits |
Дата | |
Msg-id | 24728.1320678728@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | synchronous commit vs. hint bits (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: synchronous commit vs. hint bits
Re: synchronous commit vs. hint bits |
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > SetHintBits() can't set HEAP_XMIN_COMMITTED or HEAP_XMAX_COMMITTED > hints until the commit record has been durably flushed to disk. It > turns out that can cause a major performance regression on systems > with many CPU cores. It seems to me that you've jumped to proposing solutions before you know where the problem actually is --- or at least, if you do know where the problem is, you didn't explain it. Is the cost in repeating clog lookups, or in testing to determine whether it's safe to set the bit yet, or is it contention associated with one or the other of those? regards, tom lane
В списке pgsql-hackers по дате отправления: