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

From Peter Eisentraut
Subject Re: TODO: Add a GUC to control whether BEGIN inside
Date
Msg-id 200701021150.43684.peter_e@gmx.net
Whole thread Raw
In response to Re: TODO: Add a GUC to control whether BEGIN inside  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Am Donnerstag, 28. Dezember 2006 19:52 schrieb Tom Lane:
> 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.

But this option would not, in fact, change the transaction-boundary semantics.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: effective_cache_size vs units
Next
From: Peter Eisentraut
Date:
Subject: Re: TODO: Add a GUC to control whether BEGIN inside