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 200612281757.kBSHvPP15655@momjian.us
Whole thread Raw
In response to TODO: Add a GUC to control whether BEGIN inside a transcation should abort the transaction.  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: TODO: Add a GUC to control whether BEGIN inside  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: TODO: Add a GUC to control whether BEGIN inside  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Joshua D. Drake wrote:
> Hello,
> 
> Is this really a TODO or is this someone being overzealous with the TODO
> list?

>  Add a GUC to control whether BEGIN inside a transcation should abort
> the transaction.

Well, right now, BEGIN inside a transaction just issues a warning:
test=> BEGIN;BEGINtest=> BEGIN;WARNING:  there is already a transaction in progressBEGINtest=> SELECT 1;
?column?----------       1(1 row)test=> COMMIT;COMMIT
 

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.

--  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: "Jim C. Nasby"
Date:
Subject: Re: Load distributed checkpoint
Next
From: "Joshua D. Drake"
Date:
Subject: TODO: GNU TLS