Transaction control in shards through PLPROXY

Поиск
Список
Период
Сортировка
От Granthana Biswas
Тема Transaction control in shards through PLPROXY
Дата
Msg-id CAAPsc-SGY4cNfu2G87f=2MVuGUPFQCPr7-vs47O77wvBVG6h0g@mail.gmail.com
обсуждение исходный текст
Ответы Re: Transaction control in shards through PLPROXY  (Sergey Konoplev <gray.ru@gmail.com>)
Список 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

В списке pgsql-general по дате отправления:

Предыдущее
От: hubert depesz lubaczewski
Дата:
Сообщение: Re: How can you get "WAL segment has already been removed" when doing synchronous replication ?!
Следующее
От: Steven Schlansker
Дата:
Сообщение: Re: backend hangs at sendto() and can't be terminated