Re: [HACKERS] BEGIN inside transaction should be an error - Mailing list pgsql-patches

From Tom Lane
Subject Re: [HACKERS] BEGIN inside transaction should be an error
Date
Msg-id 26860.1148661798@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] BEGIN inside transaction should be an error  ("Gurjeet Singh" <singh.gurjeet@gmail.com>)
List pgsql-patches
"Gurjeet Singh" <singh.gurjeet@gmail.com> writes:
> Here's the patch:

Wrong default (there was no consensus for changing the default behavior,
and you need to tone down the description strings).  A less verbose
GUC variable name would be a good idea, too.  Something like
"error_double_begin" would be more in keeping with most of our other names.

Doesn't actually *honor* the GUC variable, just changes the behavior
outright.  This betrays a certain lack of testing.

Also, lacks documentation.  Please grep the tree for all references to
some existing GUC variable(s) to see what you missed.

            regards, tom lane

pgsql-patches by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] BEGIN inside transaction should be an error
Next
From: Tom Lane
Date:
Subject: Re: Binary COPY for psql