| From: | Granthana Biswas <granthana(dot)biswas(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Transaction control in shards through PLPROXY |
| Date: | 2013-07-11 05:20:28 |
| Message-ID: | CAAPsc-SGY4cNfu2G87f=2MVuGUPFQCPr7-vs47O77wvBVG6h0g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
Even though this mailing list is for postgresql users only, I am
sending this query
related to postgresql sharding in case anyone has already faced this
problem while
sharding their database.
Inspite of being aware that PLPROXY does autocommit for DML functions called
on shards, I was wondering if there is any way around to put a set of DML
functions called from Router on shards inside a transaction so that all
updates on shards can be rolled back if any one among the set fails?
It would be great if anyone has already done this in their sharded database.
I was looking into transaction manager but it handles only one DML function
at a time.
Many Thanks,
GB
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jov | 2013-07-11 06:06:54 | Re: Can we specify transaction level when connectting to external postgresql server via postgres_fdw |
| Previous Message | guxiaobo1982 | 2013-07-11 03:31:31 | Can we specify transaction level when connectting to external postgresql server via postgres_fdw |