Re: Page-at-a-time Locking Considerations

Поиск
Список
Период
Сортировка
Искать
От
Alvaro Herrera
Тема
Re: Page-at-a-time Locking Considerations
Дата
Msg-id
20080204204435.GJ16380@alvh.no-ip.org
Ответ на
Список
Дерево обсуждения
Page-at-a-time Locking Considerations Simon Riggs <simon@2ndquadrant.com>
Re: Page-at-a-time Locking Considerations Bruce Momjian <bruce@momjian.us>
Re: Page-at-a-time Locking Considerations Simon Riggs <simon@2ndquadrant.com>
Re: Page-at-a-time Locking Considerations Tom Lane <tgl@sss.pgh.pa.us>
Re: Page-at-a-time Locking Considerations Simon Riggs <simon@2ndquadrant.com>
Re: Page-at-a-time Locking Considerations Gregory Stark <stark@enterprisedb.com>
Re: Page-at-a-time Locking Considerations Simon Riggs <simon@2ndquadrant.com>
Re: Page-at-a-time Locking Considerations Simon Riggs <simon@2ndquadrant.com>
Re: Page-at-a-time Locking Considerations Alvaro Herrera <alvherre@commandprompt.com>
Re: Page-at-a-time Locking Considerations Simon Riggs <simon@2ndquadrant.com>
Re: Page-at-a-time Locking Considerations Alvaro Herrera <alvherre@commandprompt.com>
Re: Page-at-a-time Locking Considerations "Heikki Linnakangas" <heikki@enterprisedb.com>
Re: Page-at-a-time Locking Considerations Tom Lane <tgl@sss.pgh.pa.us>
Re: Page-at-a-time Locking Considerations Alvaro Herrera <alvherre@commandprompt.com>
Re: Page-at-a-time Locking Considerations Zdenek Kotala <Zdenek.Kotala@Sun.COM>
Re: Page-at-a-time Locking Considerations Tom Lane <tgl@sss.pgh.pa.us>
Re: Page-at-a-time Locking Considerations Zdenek Kotala <Zdenek.Kotala@Sun.COM>
Re: Page-at-a-time Locking Considerations Tom Lane <tgl@sss.pgh.pa.us>
Re: Page-at-a-time Locking Considerations Zdenek Kotala <Zdenek.Kotala@Sun.COM>
Re: Page-at-a-time Locking Considerations Bruce Momjian <bruce@momjian.us>
Re: Page-at-a-time Locking Considerations Gregory Stark <stark@enterprisedb.com>
Re: Page-at-a-time Locking Considerations Zdenek Kotala <Zdenek.Kotala@Sun.COM>
Re: Page-at-a-time Locking Considerations Gregory Stark <stark@enterprisedb.com>
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 по дате отправления
От: Alvaro Herrera
Дата:
От: Simon Riggs
Дата:
FAQ