Re: remove upsert example from docs

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>
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 19:24:47
Message-ID: 201102171924.p1HJOl010740@momjian.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Marko Tiikkaja wrote:
> 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.

OK, sentence removed. Thanks.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ It's impossible for everything to be true. +

Attachment Content-Type Size
/rtmp/diff text/x-diff 750 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-02-17 19:28:57 Re: Rewrite, normal execution vs. EXPLAIN ANALYZE
Previous Message Andrew Dunstan 2011-02-17 19:04:59 Re: Re: [COMMITTERS] pgsql: Fix blatantly uninitialized variable in recent commit.