Re: Page-at-a-time Locking Considerations
От | Alvaro Herrera |
---|---|
Тема | Re: Page-at-a-time Locking Considerations |
Дата | |
Msg-id | 20080204204435.GJ16380@alvh.no-ip.org обсуждение исходный текст |
Ответ на | Re: Page-at-a-time Locking Considerations (Gregory Stark <stark@enterprisedb.com>) |
Ответы |
Re: Page-at-a-time Locking Considerations
Re: Page-at-a-time Locking Considerations |
Список | pgsql-hackers |
Gregory Stark wrote: > I wonder how hard it would be to shove the clog into regular shared memory > pages and let the clock sweep take care of adjusting the percentage of shared > mem allocated to the clog versus data pages. Hmm, this is an interesting idea. I wonder what would happen if we let other SLRU users go into shared buffers too -- for example it has been reported several times that pg_subtrans thrashing can cause severe problems in case of long running transactions. (I wonder whether pg_subtrans would occupy a big portion of shared buffers if we let it go unchecked). -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support
В списке pgsql-hackers по дате отправления: