pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Don't need transaction integrity - can I turn it off
6+ messages / 5 participants
[nested] [flat]

* Don't need transaction integrity - can I turn it off
@ 1999-08-27 05:16 Hamid Khoshnevis <hamid@emarq.com>
  1999-08-27 05:51 ` Re: [SQL] Don't need transaction integrity - can I turn it off Bruce Momjian <maillist@candle.pha.pa.us>
  1999-08-27 21:53 ` Re: [SQL] Don't need transaction integrity - can I turn it off Michael Richards <miker@scifair.acadiau.ca>
  0 siblings, 2 replies; 6+ messages in thread

From: Hamid Khoshnevis @ 1999-08-27 05:16 UTC (permalink / raw)
  To: pgsql-sql

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 some
insert/updates.

hamid




^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [SQL] Don't need transaction integrity - can I turn it off
  1999-08-27 05:16 Don't need transaction integrity - can I turn it off Hamid Khoshnevis <hamid@emarq.com>
@ 1999-08-27 05:51 ` Bruce Momjian <maillist@candle.pha.pa.us>
  1999-08-27 08:33   ` Re: [SQL] Don't need transaction integrity - can I turn it off Oliver Elphick <olly@lfix.co.uk>
  1 sibling, 1 reply; 6+ messages in thread

From: Bruce Momjian @ 1999-08-27 05:51 UTC (permalink / raw)
  To: Hamid Khoshnevis <hamid@emarq.com>; +Cc: pgsql-sql

[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 some
> insert/updates.

Yes, we have no-fsync option.  See FAQ.

-- 
  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



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [SQL] Don't need transaction integrity - can I turn it off
  1999-08-27 05:16 Don't need transaction integrity - can I turn it off Hamid Khoshnevis <hamid@emarq.com>
  1999-08-27 05:51 ` Re: [SQL] Don't need transaction integrity - can I turn it off Bruce Momjian <maillist@candle.pha.pa.us>
@ 1999-08-27 08:33   ` Oliver Elphick <olly@lfix.co.uk>
  1999-08-27 13:45     ` Re: [SQL] Don't need transaction integrity - can I turn it off Tom Lane <tgl@sss.pgh.pa.us>
  1999-08-27 14:22     ` Re: [SQL] Don't need transaction integrity - can I turn it off Bruce Momjian <maillist@candle.pha.pa.us>
  0 siblings, 2 replies; 6+ messages in thread

From: Oliver Elphick @ 1999-08-27 08:33 UTC (permalink / raw)
  To: Bruce Momjian <maillist@candle.pha.pa.us>; +Cc: Hamid Khoshnevis <hamid@emarq.com>; pgsql-sql

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?

-- 
      Vote against SPAM: http://www.politik-digital.de/spam/
                 ========================================
Oliver Elphick                                Oliver.Elphick@lfix.co.uk
Isle of Wight                              http://www.lfix.co.uk/oliver
               PGP key from public servers; key ID 32B8FAA1
                 ========================================
     "But the end of all things is at hand; be ye therefore 
      sober, and watch unto prayer. And above all things 
      have fervent love among yourselves; for love shall  
      cover the multitude of sins."      I Peter 4:7,8





^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [SQL] Don't need transaction integrity - can I turn it off
  1999-08-27 05:16 Don't need transaction integrity - can I turn it off Hamid Khoshnevis <hamid@emarq.com>
  1999-08-27 05:51 ` Re: [SQL] Don't need transaction integrity - can I turn it off Bruce Momjian <maillist@candle.pha.pa.us>
  1999-08-27 08:33   ` Re: [SQL] Don't need transaction integrity - can I turn it off Oliver Elphick <olly@lfix.co.uk>
@ 1999-08-27 13:45     ` Tom Lane <tgl@sss.pgh.pa.us>
  1 sibling, 0 replies; 6+ messages in thread

From: Tom Lane @ 1999-08-27 13:45 UTC (permalink / raw)
  To: Oliver Elphick <olly@lfix.co.uk>; +Cc: Bruce Momjian <maillist@candle.pha.pa.us>; Hamid Khoshnevis <hamid@emarq.com>; pgsql-sql

"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



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [SQL] Don't need transaction integrity - can I turn it off
  1999-08-27 05:16 Don't need transaction integrity - can I turn it off Hamid Khoshnevis <hamid@emarq.com>
  1999-08-27 05:51 ` Re: [SQL] Don't need transaction integrity - can I turn it off Bruce Momjian <maillist@candle.pha.pa.us>
  1999-08-27 08:33   ` Re: [SQL] Don't need transaction integrity - can I turn it off Oliver Elphick <olly@lfix.co.uk>
@ 1999-08-27 14:22     ` Bruce Momjian <maillist@candle.pha.pa.us>
  1 sibling, 0 replies; 6+ messages in thread

From: Bruce Momjian @ 1999-08-27 14:22 UTC (permalink / raw)
  To: Oliver Elphick <olly@lfix.co.uk>; +Cc: Hamid Khoshnevis <hamid@emarq.com>; pgsql-sql

> 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



^ permalink  raw  reply  [nested|flat] 6+ messages in thread

* Re: [SQL] Don't need transaction integrity - can I turn it off
  1999-08-27 05:16 Don't need transaction integrity - can I turn it off Hamid Khoshnevis <hamid@emarq.com>
@ 1999-08-27 21:53 ` Michael Richards <miker@scifair.acadiau.ca>
  1 sibling, 0 replies; 6+ messages in thread

From: Michael Richards @ 1999-08-27 21:53 UTC (permalink / raw)
  To: Hamid Khoshnevis <hamid@emarq.com>; +Cc: pgsql-sql

On Thu, 26 Aug 1999, Hamid Khoshnevis wrote:

> 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 some
> insert/updates.

Personally, I'd set it all up and give it a whirl first. Often I've found
that these things work better than I expected and don't need to be fiddled
with to get expected speeds.

-Michael




^ permalink  raw  reply  [nested|flat] 6+ messages in thread


end of thread, other threads:[~1999-08-27 21:53 UTC | newest]

Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-08-27 05:16 Don't need transaction integrity - can I turn it off Hamid Khoshnevis <hamid@emarq.com>
1999-08-27 05:51 ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-08-27 08:33   ` Oliver Elphick <olly@lfix.co.uk>
1999-08-27 13:45     ` Tom Lane <tgl@sss.pgh.pa.us>
1999-08-27 14:22     ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-08-27 21:53 ` Michael Richards <miker@scifair.acadiau.ca>

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