Re: Database Integrity

From: "Jean-Yves F(dot) Barbier" <12ukwn(at)gmail(dot)com>
To: pgsql-novice(at)postgresql(dot)org
Subject: Re: Database Integrity
Date: 2011-11-18 19:48:57
Message-ID: 20111118204857.2ee4d927@anubis.defcon1
Views: Raw Message | Whole Thread | Download mbox
Lists: pgsql-novice

On Fri, 18 Nov 2011 20:44:33 +0100
"Jean-Yves F. Barbier" <12ukwn(at)gmail(dot)com> wrote:

> AFAIK no because even if you're not in your transaction, Pg opens its own (hence
> rollback if something bad happens).

Oops: forgot to say that in this case, you'll loose the concurrency you
could have with SET TRANSACTION SERIALIZABLE, which is bad if there are
many concurrent DELETEs & users making them.

Evening hours "all clear" for romance!
(Tell mate you have to work late.)

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Jane Geering 2011-11-18 23:27:18 Access to pg_hba.conf
Previous Message Daniel Staal 2011-11-18 19:46:48 Re: Database Integrity