| From: | Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> |
|---|---|
| To: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> |
| Cc: | A B <gentosaker(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Running PostgreSQL as fast as possible no matter the consequences |
| Date: | 2010-11-05 16:25:55 |
| Message-ID: | 4CD43013.7000906@vmsinfo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Devrim GÜNDÜZ wrote:
> On Fri, 2010-11-05 at 11:59 +0100, A B wrote:
>
>> 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?
>>
>
> You can initdb to ramdisk, if you have enough RAM. It will fast, really.
>
>
That is approximately the same thing as the answer to the question
whether Ford Taurus can reach 200mph.
It can, just once, if you run it down the cliff.
--
Mladen Gogala
Sr. Oracle DBA
1500 Broadway
New York, NY 10036
(212) 329-5251
http://www.vmsinfo.com
The Leader in Integrated Media Intelligence Solutions
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Klemme | 2010-11-05 17:30:54 | Re: Simple (hopefully) throughput question? |
| Previous Message | Devrim GÜNDÜZ | 2010-11-05 15:23:35 | Re: Running PostgreSQL as fast as possible no matter the consequences |