Am Donnerstag, 28. Dezember 2006 18:57 schrieb Bruce Momjian:
> I think you can make the case that this should be an error, or at least
> that's how it got on the TODO list.  I can always remove it if people
> don't want the item completed.

The reason this was added is that modular applications expect that a locally 
issued BEGIN ... COMMIT executes a transaction, whereas now you don't know 
what you're getting.  I think this change would have merit.

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

In response to

• Re: TODO: Add a GUC to control whether BEGIN inside at 2006-12-28 17:57:25 from Bruce Momjian

Responses

• Re: TODO: Add a GUC to control whether BEGIN inside at 2007-01-02 15:00:24 from Tom Lane
• Re: TODO: Add a GUC to control whether BEGIN inside at 2007-01-02 17:26:05 from Joshua D. Drake

pgsql-hackers by date

Next:	From: Neil Conway	Date: 2007-01-02 14:19:50
	Subject: Re: float8 width_bucket function
Previous:	From: Peter Eisentraut	Date: 2007-01-02 10:50:41
	Subject: Re: TODO: Add a GUC to control whether BEGIN inside