| From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
|---|---|
| To: | |
| Cc: | "Vogt\, Michael" <Michael(dot)Vogt(at)united-security-providers(dot)ch>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Autocommit off - commits/rollbacks |
| Date: | 2011-03-29 07:24:06 |
| Message-ID: | 871v1qs82x.fsf@comcast.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Craig Ringer <craig(at)postnewspapers(dot)com(dot)au> writes:
> On 03/14/2011 10:55 PM, Vogt, Michael wrote:
>
>> Hey all
>>
>> I have a question, using the autocommit off option in postgres.
>>
>> As starting position I use a table called xxx.configuration using a
>> unique id constraint.
>>
>> Why does postgres rollback the whole transaction after an error?
>
> It's a PostgreSQL limitation (or, arguably, optimization). When a
Well, any transactional RDBMS whatsoever should behave that way. Hardly
a PostgreSQL exclusive feature :-)
--
Jerry Sievers
e: gsievers19(at)comcast(dot)net
p: 305.321.1144
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zheng Yang | 2011-03-29 11:28:57 | Re: foreign data wrappers |
| Previous Message | Jerry Sievers | 2011-03-29 07:17:31 | Re: What could keep a connection / query alive? |