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

From Tom Lane
Subject Re: TODO: Add a GUC to control whether BEGIN inside
Date
Msg-id 22676.1167331946@sss.pgh.pa.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
Re: TODO: Add a GUC to control whether BEGIN inside
List pgsql-hackers
"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.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Load distributed checkpoint
Next
From: Stephen Frost
Date:
Subject: Re: TODO: GNU TLS