Skip site navigation (1) Skip section navigation (2)

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

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,"Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>,Bruce Momjian <bruce(at)momjian(dot)us>
Subject: Re: TODO: Add a GUC to control whether BEGIN inside
Date: 2007-01-02 10:50:41
Message-ID: 200701021150.43684.peter_e@gmx.net (view raw or flat)
Thread:
Lists: 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/

In response to

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2007-01-02 10:53:17
Subject: Re: TODO: Add a GUC to control whether BEGIN inside
Previous:From: Peter EisentrautDate: 2007-01-02 10:48:25
Subject: Re: effective_cache_size vs units

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group