Re: remove upsert example from docs

From: Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Merlin Moncure <mmoncure(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: remove upsert example from docs
Date: 2011-02-17 18:47:18
Message-ID: 4D5D6D36.3070805@cs.helsinki.fi
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2011-02-17 8:37 PM +0200, Bruce Momjian wrote:
> Marko Tiikkaja wrote:
>> The problem with the "safe" way is that it's not safe if called in a
>> transaction with isolation level set to SERIALIZABLE.
>
> Good analysis. Documentation patch attached and applied.

The "safe way" I was referring to above was the LOCK TABLE method, not
the one described in the documentation, so the remark about READ
COMMITTED in the patch should be removed. The first part looks fine though.

Regards,
Marko Tiikkaja

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-02-17 18:53:04 Re: contrib loose ends: 9.0 to 9.1 incompatibilities
Previous Message Robert Haas 2011-02-17 18:43:35 Re: contrib loose ends: 9.0 to 9.1 incompatibilities