Re: limiting hint bit I/O
От | Robert Haas |
---|---|
Тема | Re: limiting hint bit I/O |
Дата | |
Msg-id | AANLkTim0T=oDKTNdj8sscQtca04uyfJyQd8NdBa9hvf4@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: limiting hint bit I/O ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: limiting hint bit I/O
|
Список | pgsql-hackers |
On Fri, Jan 14, 2011 at 1:34 PM, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote: > Robert Haas <robertmhaas@gmail.com> wrote: > >> I'm hoping some will pick it up and play with it some more (hint, >> hint). > > That was a bit of a pun, eh? Unintentional... > Anyway, there are so many ideas in this area, it's hard to keep them > all straight. Personally, if I was going to start with something, > it would probably be to better establish what the impact is on > various workloads of *eliminating* hint bits. If the impact is > negative to a significant degree, my next step might be to try > background *freezing* of tuples (in a manner somewhat similar to > what you've done in this test) with the hint bits gone. Background freezing plays havoc with Hot Standby, and this test is sufficient to show that eliminating hint bits altogether would a significant regression on some workloads. I don't think either of those ideas can get off the ground. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: