Re: Running PostgreSQL as fast as possible no matter the consequences
От | Marti Raudsepp |
---|---|
Тема | Re: Running PostgreSQL as fast as possible no matter the consequences |
Дата | |
Msg-id | AANLkTi=9CL-O=D_eiCxx7R=1zkGhimAotnGgB_WsvC2-@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Running PostgreSQL as fast as possible no matter the consequences (A B <gentosaker@gmail.com>) |
Ответы |
Re: Running PostgreSQL as fast as possible no matter the consequences
Re: Running PostgreSQL as fast as possible no matter the consequences |
Список | pgsql-performance |
On Fri, Nov 5, 2010 at 13:32, A B <gentosaker@gmail.com> wrote: > I was just thinking about the case where I will have almost 100% > selects, but still needs something better than a plain key-value > storage so I can do some sql queries. > The server will just boot, load data, run, hopefully not crash but if > it would, just start over with load and run. If you want fast read queries then changing fsync/full_page_writes/synchronous_commit won't help you. Just follow the regular tuning guide. shared_buffers, effective_cache_size, work_mem, default_statistics_target can make a difference. http://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server Regards, Marti
В списке pgsql-performance по дате отправления: