Re: Tricky bugs in concurrent index build

From: David Fetter <david(at)fetter(dot)org>
To: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Cc: Gregory Stark <stark(at)enterprisedb(dot)com>, 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 15:06:55
Message-ID: 20060826150655.GK11427@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 25, 2006 at 08:02:21PM -0500, Jim C. Nasby wrote:
> 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

+1 here, too :)

Cheers,
D
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter

Remember to vote!

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-08-26 15:39:32 Re: Tricky bugs in concurrent index build
Previous Message David Fetter 2006-08-26 15:04:48 Re: [HACKERS] New XML section for documentation