Received: from candle.pha.pa.us (root@s5-03.ppp.op.net [209.152.195.67]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA89048 for ; Fri, 27 Aug 1999 10:25:52 -0400 (EDT) (envelope-from maillist@candle.pha.pa.us) Received: (from maillist@localhost) by candle.pha.pa.us (8.9.0/8.9.0) id KAA20361; Fri, 27 Aug 1999 10:22:29 -0400 (EDT) From: Bruce Momjian Message-Id: <199908271422.KAA20361@candle.pha.pa.us> Subject: Re: [SQL] Don't need transaction integrity - can I turn it off In-Reply-To: <199908270833.JAA17612@linda.lfix.co.uk> from Oliver Elphick at "Aug 27, 1999 09:33:44 am" To: Oliver Elphick Date: Fri, 27 Aug 1999 10:22:29 -0400 (EDT) CC: Hamid Khoshnevis , pgsql-sql@postgreSQL.org X-Mailer: ELM [version 2.4ME+ PL56 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit > Bruce Momjian wrote: > >[Charset iso-8859-1 unsupported, filtering to ASCII...] > >> My application requires very fast update/insert- where I am told mySQL > >> shines. Can I turn off commit/rollback in Postgres so as to dramatically > >> speed up insert/updates. I understand and accept the cost of dropping som > >e > >> insert/updates. > > > >Yes, we have no-fsync option. See FAQ. > > But that has to do with not forcing a sync to disk after every write. > I've never heard of an ability to disable transactions; isn't every > operation outside an explicitly-declared transaction made a single > separate transaction by default? Yes, you are right. No way to disable transactions. -- Bruce Momjian | http://www.op.net/~candle maillist@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026