Chris Browne wrote: > gentosaker@xxxxxxxxx (A B) writes: > > 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? > > Use /dev/null. It is web scale, and there are good tutorials. > > But seriously, there *are* cases where "blind speed" is of use. When > loading data into a fresh database is a good time for this; if things > fall over, it may be pretty acceptable to start "from scratch" with > mkfs/initdb. > > I'd: > - turn off fsync > - turn off synchronous commit > - put as much as possible onto Ramdisk/tmpfs/similar as possible FYI, we do have a documentation section about how to configure Postgres for improved performance if you don't care about durability: http://developer.postgresql.org/pgdocs/postgres/non-durability.html -- Bruce Momjian <bruce@xxxxxxxxxx> http://momjian.us EnterpriseDB http://enterprisedb.com + It's impossible for everything to be true. + -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
