From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Rajeev rastogi <rajeev(dot)rastogi(at)huawei(dot)com> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Autonomous Transaction (WIP) |
Date: | 2014-04-07 10:11:38 |
Message-ID: | CAFj8pRA8WCgTFVtHT1X1nLbCurX0-PqwrZxfrvVwMRni1rKJDA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2014-04-07 11:59 GMT+02:00 Rajeev rastogi <rajeev(dot)rastogi(at)huawei(dot)com>:
> On 07 April 2014 12:12, Pavel Stehule wrote:
>
> >+1 for feature
>
> Thanks
>
>
>
> >-1 for Oracle syntax - it is hardly inconsistent with Postgres
>
> We can discuss and come out with the syntax based on everyone agreement.
>
> >Autonomous transactions should be used everywhere - not only in plpgsql
>
>
>
> Yes you are right. I am not planning to support only using plpgsql.
> Initially we can support this
>
> Using the standalone SQL-commands and then later we can enhance based on
> this infrastructure
>
> to be used using plpgsql, triggers.
>
ok
long time I though about this feature.
I am thinking so this should be fully isolated transaction - it should not
be subtransaction, because then you can break database consistency - RI
I am happy so someone does this job
Regards
Pavel
>
>
> *Thanks and Regards,*
>
> *Kumar Rajeev Rastogi *
>
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Atri Sharma | 2014-04-07 10:16:42 | Re: Autonomous Transaction (WIP) |
Previous Message | Rajeev rastogi | 2014-04-07 09:59:00 | Re: Autonomous Transaction (WIP) |