Re: Running PostgreSQL as fast as possible no matter the consequences
От | A B |
---|---|
Тема | Re: Running PostgreSQL as fast as possible no matter the consequences |
Дата | |
Msg-id | AANLkTin+ZRe5mEOj72ga8xOfbULpYn6kwH4hy_JCBYm2@mail.gmail.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
Re: Running PostgreSQL as fast as possible no matter the consequences Re: Running PostgreSQL as fast as possible no matter the consequences |
Список | pgsql-performance |
>> 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? >> > > > I'm just curious, what do you need that for? > > regards > Szymon 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.
В списке pgsql-performance по дате отправления: