Re: Running PostgreSQL as fast as possible no matter the consequences

Поиск
Список
Период
Сортировка
Искать
От
Craig Ringer
Тема
Re: Running PostgreSQL as fast as possible no matter the consequences
Дата
Msg-id
4CD3EA2D.3050403@postnewspapers.com.au
Ответ на
Running PostgreSQL as fast as possible no matter the consequences (A B)
Список
Дерево обсуждения
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 Devrim GÜNDÜZ <devrim@gunduz.org>
Re: Running PostgreSQL as fast as possible no matter the consequences Mladen Gogala <mladen.gogala@vmsinfo.com>
Re: Running PostgreSQL as fast as possible no matter the consequences Craig Ringer <craig@postnewspapers.com.au>
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 Guillaume Cottenceau <gc@mnc.ch>
Re: Running PostgreSQL as fast as possible no matter the consequences Marti Raudsepp <marti@juffo.org>
Re: Running PostgreSQL as fast as possible no matter the consequences Guillaume Cottenceau <gc@mnc.ch>
Re: Running PostgreSQL as fast as possible no matter the consequences Thom Brown <thom@linux.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 Thom Brown <thom@linux.com>
Re: Running PostgreSQL as fast as possible no matter the consequences Szymon Guz <mabewlun@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 Craig Ringer <craig@postnewspapers.com.au>
Re: Running PostgreSQL as fast as possible no matter the consequences Marti Raudsepp <marti@juffo.org>
Re: Running PostgreSQL as fast as possible no matter the consequences Guillaume Cottenceau <gc@mnc.ch>
Re: Running PostgreSQL as fast as possible no matter the consequences Jon Nelson <jnelson+pgsql@jamponi.net>
Re: Running PostgreSQL as fast as possible no matter the consequences Robert Haas <robertmhaas@gmail.com>
Re: Running PostgreSQL as fast as possible no matter the consequences Andy Colson <andy@squeakycode.net>
Re: Running PostgreSQL as fast as possible no matter the consequences Robert Haas <robertmhaas@gmail.com>
Re: Running PostgreSQL as fast as possible no matter the consequences Thom Brown <thom@linux.com>
Re: Running PostgreSQL as fast as possible no matter the consequences "Lello, Nick" <nick.lello@rentrakmail.com>
Re: Running PostgreSQL as fast as possible no matter the consequences Klaus Ita <klaus@worstofall.com>
Re: Running PostgreSQL as fast as possible no matter the consequences Dimitri Fontaine <dimitri@2ndQuadrant.fr> 
On 05/11/10 18:59, A B wrote:
> Hi there.
> 
> If you just wanted PostgreSQL to go as fast as possible WITHOUT any
> care for your data (you accept 100% dataloss and datacorruption if any
> error should occur), what settings should you use then?

Others have suggested appropriate parameters ("running with scissors").

I'd like to add something else to the discussion: have you looked at
memcached yet? Or pgpool? If you haven't, start there.

-- 
Craig Ringer

Tech-related writing: http://soapyfrogs.blogspot.com/
В списке pgsql-performance по дате отправления
Предыдущее
От: A B
Дата:
Следующее
От: A B
Дата:
FAQ