From: Tom Lane <tgl@sss.pgh.pa.us>
To: Oliver Elphick <olly@lfix.co.uk>
Cc: Bruce Momjian <maillist@candle.pha.pa.us>
Cc: Hamid Khoshnevis <hamid@emarq.com>
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Don't need transaction integrity - can I turn it off
Date: Fri, 27 Aug 1999 09:45:11 -0400
Message-ID: <6401.935761511@sss.pgh.pa.us> (raw)
In-Reply-To: <199908270833.JAA17612@linda.lfix.co.uk>
"Oliver Elphick" <olly@lfix.co.uk> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, olly@lfix.co.uk, maillist@candle.pha.pa.us, hamid@emarq.com
Subject: Re: [SQL] Don't need transaction integrity - can I turn it off
In-Reply-To: <6401.935761511@sss.pgh.pa.us>
References: <199908270833.JAA17612@linda.lfix.co.uk> <6401.935761511@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox