Re: Tricky bugs in concurrent index build

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Zeugswetter Andreas DCP SD <ZeugswetterA(at)spardat(dot)at>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Tricky bugs in concurrent index build
Date: 2006-08-26 01:02:21
Message-ID: 20060826010221.GD73562@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 25, 2006 at 06:57:58PM +0100, Gregory Stark wrote:
> I'll use this opportunity to plug that feature again. I think most people
> should use autocommit off with on_error_rollack on for most of their daily
> use. Being able to double check the results of my ad-hoc updates before
> committing them saved me more headaches than I can count with Oracle.
> Autocommit off only became practical for interactive use with postgres when
> savepoints showed up.

+1
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim C. Nasby 2006-08-26 01:05:09 Re: Tricky bugs in concurrent index build
Previous Message Jim C. Nasby 2006-08-26 00:55:40 Re: default child of partition master