Re: [PATCHES] Reorganization of spinlock defines
От | Marc G. Fournier |
---|---|
Тема | Re: [PATCHES] Reorganization of spinlock defines |
Дата | |
Msg-id | 20030912100638.K82880@ganymede.hub.org обсуждение исходный текст |
Ответ на | Re: [PATCHES] Reorganization of spinlock defines (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [PATCHES] Reorganization of spinlock defines
Re: [PATCHES] Reorganization of spinlock defines |
Список | pgsql-hackers |
On Fri, 12 Sep 2003, Tom Lane wrote: > "Marc G. Fournier" <scrappy@postgresql.org> writes: > >> Right, though I am not sure people will know _slow_ configuration vs. > >> PostgreSQL is slow. > > > No, but definitely something for those discussion performance to add > > to their checklist :) > > > BTW, post-compile, running system ... how do you check this? Or can you? > > If we force people to give a --without-spinlocks config option to build > that way, then `pg_config --configure' will reveal the dirty deed ... That's not quite what I meant :) Right now, if I understood what Bruce was saying, if someone doesn't have spinlocks, it switches to using SysV Messenging, correct? In the current system, is there anything that one can do on a running, live system, to detect that you aren't using spinlocks?
В списке pgsql-hackers по дате отправления: