Re: [HACKERS] TRANSACTIONS

From: Don Baccus <dhogaza(at)pacifier(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jose Soares <jose(at)sferacarta(dot)com>
Cc: hackers <pgsql-hackers(at)postgreSQL(dot)org>, general <pgsql-general(at)postgreSQL(dot)org>
Subject: Re: [HACKERS] TRANSACTIONS
Date: 2000-02-22 18:47:16
Message-ID: 3.0.1.32.20000222104716.010bd050@mail.pacifier.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

At 11:32 AM 2/22/00 -0500, Tom Lane wrote:

>I see no way that allowing the transaction to commit after an overflow
>can be called consistent with the spec.

You are absolutely right. The whole point is that either a) everything
commits or b) nothing commits.

Having some kinds of exceptions allow a partial commit while other
exceptions rollback the transaction seems like a very error-prone
programming environment to me.

- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Daniel Forsyth 2000-02-22 20:40:24 unsubscribe
Previous Message Jeff MacDonald 2000-02-22 18:08:31 Re: [GENERAL] Calender

Browse pgsql-hackers by date

  From Date Subject
Next Message Don Baccus 2000-02-22 18:49:54 Re: [HACKERS] PostgreSQL v7.0 goes Beta ...
Previous Message Nora Luz Escobar López 2000-02-22 18:43:11 subcription