Re: Autonomous Transaction is back - Mailing list pgsql-hackers

From Rajeev rastogi
Subject Re: Autonomous Transaction is back
Date
Msg-id BF2827DCCE55594C8D7A8F7FFD3AB7715990AAC6@szxeml521-mbs.china.huawei.com
Whole thread Raw
In response to Re: Autonomous Transaction is back  (Josh Berkus <josh@agliodbs.com>)
List pgsql-hackers
On 28 July 2015 03:21, Josh Berkus Wrote:
On 07/27/2015 02:47 AM, Rajeev rastogi wrote:
>>> Why have any fixed maximum?
>> Since we are planning to have nested autonomous transaction, so it is required to have limit on this so that
resourcescan be controlled.
 

>Is there a particular reason why this limit wouldn't just be max_stack_depth?

We will require to allocate some initial resources in order to handle all nested autonomous transaction. 
So I think it is better to have some different configuration parameter.

Thanks and Regards,
Kumar Rajeev Rastogi

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: multivariate statistics / patch v7
Next
From: Heikki Linnakangas
Date:
Subject: Re: Configurable location for extension .control files