tables/indexes/logs on different volumes
От | ncm@zembu.com (Nathan Myers) |
---|---|
Тема | tables/indexes/logs on different volumes |
Дата | |
Msg-id | 20010425132545.C1692@store.zembu.com обсуждение исходный текст |
Ответ на | Re: Re: refusing connections based on load ... (The Hermit Hacker <scrappy@hub.org>) |
Список | pgsql-hackers |
On Wed, Apr 25, 2001 at 09:41:57AM -0300, The Hermit Hacker wrote: > On Tue, 24 Apr 2001, Nathan Myers wrote: > > > On Tue, Apr 24, 2001 at 11:28:17PM -0300, The Hermit Hacker wrote: > > > I have a Dual-866, 1gig of RAM and strip'd file systems ... this past > > > week, I've hit many times where CPU usage is 100%, RAM is 500Meg free > > > and disks are pretty much sitting idle ... > > > > Assuming "strip'd" above means "striped", it strikes me that you > > might be much better off operating the drives independently, with > > the various tables, indexes, and logs scattered each entirely on one > > drive. > > have you ever tried to maintain a database doing this? PgSQL is > definitely not designed for this sort of setup, I had symlinks going > everywhere, and with the new numbering schema, this is even more > difficult to try and do :) Clearly you need to build a tool to organize it. It would help a lot if PG itself could provide some basic assistance, such as calling a stored procedure to generate the pathname of the file. Has there been any discussion of anything like that? Nathan Myers ncm@zembu.com
В списке pgsql-hackers по дате отправления: