Re: Transaction control in shards through PLPROXY

From: Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>
To: Granthana Biswas <granthana(dot)biswas(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Transaction control in shards through PLPROXY
Date: 2013-07-15 05:21:39
Message-ID: CAL_0b1u+arDmR5yhCs6TzzqEx6DAO_2fy8PWSj8x=iQ5_ky41g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jul 10, 2013 at 10:20 PM, Granthana Biswas
<granthana(dot)biswas(at)gmail(dot)com> wrote:
> 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 is called two-phase commit. You need to consult with this [1]
section of documentation.

[1] http://www.postgresql.org/docs/9.2/static/sql-prepare-transaction.html

--
Kind regards,
Sergey Konoplev
PostgreSQL Consultant and DBA

Profile: http://www.linkedin.com/in/grayhemp
Phone: USA +1 (415) 867-9984, Russia +7 (901) 903-0499, +7 (988) 888-1979
Skype: gray-hemp
Jabber: gray(dot)ru(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Granthana Biswas 2013-07-15 05:56:36 Re: Transaction control in shards through PLPROXY
Previous Message ktewari1 2013-07-15 02:54:35 Re: Build RPM from Postgres Source