Re: TODO: Add a GUC to control whether BEGIN inside

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: TODO: Add a GUC to control whether BEGIN inside
Date: 2006-12-28 20:44:07
Message-ID: 200612282044.kBSKi7a04021@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joshua D. Drake wrote:
> On Thu, 2006-12-28 at 13:52 -0500, Tom Lane wrote:
> > "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> > > I would say that a GUC variable for such behavior as listed in the TODO
> > > is overzealous. We should either enforce it, or not. As we do not now,
> > > there is no reason imo to change it.
> >
> > Not only is it overzealous, but the proposal to have one reflects a
> > failure to learn from history. GUC variables that change
> > transaction-boundary semantics are a bad idea, period: see autocommit.
>
> Nod. Let's get this TODO removed.

OK, removed.

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-12-28 20:55:56 Re: Load distributed checkpoint
Previous Message mark 2006-12-28 20:41:55 Re: TODO: GNU TLS