Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA50020 for ; Fri, 27 Aug 1999 09:46:45 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id JAA06403; Fri, 27 Aug 1999 09:45:12 -0400 (EDT) To: "Oliver Elphick" cc: Bruce Momjian , Hamid Khoshnevis , pgsql-sql@postgreSQL.org Subject: Re: [SQL] Don't need transaction integrity - can I turn it off In-reply-to: Your message of Fri, 27 Aug 1999 09:33:44 +0100 <199908270833.JAA17612@linda.lfix.co.uk> Date: Fri, 27 Aug 1999 09:45:11 -0400 Message-ID: <6401.935761511@sss.pgh.pa.us> From: Tom Lane "Oliver Elphick" writes: >> 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? It is, and I don't think there's any possibility of turning that off. It's too tightly integrated with the cross-backend interlocking. If you don't want transactions, and you don't want multiple backends, maybe mySQL is what you need ;-) BTW, if you're not too concerned about parallelism, one way to squeeze a little more speed is to use explicit transactions *more*, not less. The more stuff you get done between BEGIN and COMMIT, the less the transaction overhead per useful operation... regards, tom lane