Re: Constraint between 2 tables and taking a coherent snapshot of both

From: decibel <decibel(at)decibel(dot)org>
To: Ivan Sergio Borgonovo <mail(at)webthatworks(dot)it>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Constraint between 2 tables and taking a coherent snapshot of both
Date: 2009-08-06 17:39:17
Message-ID: FBC1E0BF-A99D-468A-A015-F284E05F4E36@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Jul 26, 2009, at 1:32 PM, Ivan Sergio Borgonovo wrote:
> Actually a serializable transaction doesn't even seem a too bad
> solution... but I just would like to understand better how to manage
> this situation so that I could make it as simple as possible AND
> lower as much as possible the chances that the transaction will have
> to be rolled back.

This sounds exactly what serialized transactions are for. And I would
certainly promote simplicity over worrying about things like rollback
performance.
--
Decibel!, aka Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828

In response to

Browse pgsql-general by date

  From Date Subject
Next Message david.schruth 2009-08-06 17:43:43 JOIN a UNION
Previous Message Jeff Davis 2009-08-06 17:38:37 Re: Empty Updates, ON UPDATE triggers and Rules