Re: TODO: Add a GUC to control whether BEGIN inside - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: TODO: Add a GUC to control whether BEGIN inside
Date
Msg-id 200612282044.kBSKi7a04021@momjian.us
Whole thread Raw
In response to Re: TODO: Add a GUC to control whether BEGIN inside  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: TODO: Add a GUC to control whether BEGIN inside
List pgsql-hackers
Joshua D. Drake wrote:
> On Thu, 2006-12-28 at 13:52 -0500, Tom Lane wrote:
> > "Joshua D. Drake" <jd@commandprompt.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@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: mark@mark.mielke.cc
Date:
Subject: Re: TODO: GNU TLS
Next
From: Bruce Momjian
Date:
Subject: Re: Load distributed checkpoint