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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: A B <gentosaker@xxxxxxxxx>
Subject: Re: Running PostgreSQL as fast as possible no matter the consequences
From: Szymon Guz <mabewlun@xxxxxxxxx>
Date: Fri, 5 Nov 2010 12:23:36 +0100
Cc: pgsql-performance@xxxxxxxxxxxxxx
In-reply-to: <AANLkTimcUYuutQeThCaP-077reGYWwdq-ssKwbPne8TO@xxxxxxxxxxxxxx>
References: <AANLkTimcUYuutQeThCaP-077reGYWwdq-ssKwbPne8TO@xxxxxxxxxxxxxx>

On 5 November 2010 11:59, A B <gentosaker@xxxxxxxxx> 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?

I'm just curious, what do you need that for?

regards

Szymon

Follow-Ups:
- Re: Running PostgreSQL as fast as possible no matter the consequences
  - From: A B

References:
- Running PostgreSQL as fast as possible no matter the consequences
  - From: A B

Prev by Date: Re: Running PostgreSQL as fast as possible no matter the consequences
Next by Date: Re: Running PostgreSQL as fast as possible no matter the consequences
Previous by thread: Re: Running PostgreSQL as fast as possible no matter the consequences
Next by thread: Re: Running PostgreSQL as fast as possible no matter the consequences
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux