pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Richard Broersma <richard.broersma@gmail.com>
To: wyx6fox@sina.com
To: pgsql-performance@postgresql.org
Subject:  Re: 回复:Re: [PERFORM] the jokes for pg concurrency write performance
Date: Tue, 2 Feb 2010 07:43:52 -0800
Message-ID: <396486431002020743x739a5f80od11dbb83c6e1c399@mail.gmail.com> (raw)
In-Reply-To: <20100202071154.241D94B1C71@mail175-236.sinamail.sina.com.cn>
References: <20100202071154.241D94B1C71@mail175-236.sinamail.sina.com.cn>

2010/2/1  <wyx6fox@sina.com>:

> yet, this code is just for fun , why ? because i found this code in one
> article:PostgreSQL Concurrency Issues .

I'm not familiar with the "code" that you are referring to.  Do you
have a hyper-link to it?


> Tom Lane
> Red Hat Database Group
> Red Hat, Inc.

Also, I'm not sure why you mentioned Tom's name here.  Does he have
anything to do with the "code" that you've previously mentioned?

> so many design should be better than this , But now we should talk about
> this ,I just want talk about confick update on concurrency write
> transaction.

Regarding the update conflict, what aspect of it did you want to talk
about?  Also, so that others (having much more experience that I do)
can participate in this discussion please reply-all to the email.
This will ensure that the pgsql-performance@postgresql.org mailing is
included.


-- 
Regards,
Richard Broersma Jr.

Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug



view thread (2+ messages)  latest in thread

Message-ID: <396486431002020743x739a5f80od11dbb83c6e1c399@mail.gmail.com>
Permalink:  ../396486431002020743x739a5f80od11dbb83c6e1c399@mail.gmail.com/
Also on:    postgresql.org/message-id/396486431002020743x739a5f80od11dbb83c6e1c399@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: richard.broersma@gmail.com, wyx6fox@sina.com
  Subject: Re: 回复:Re: [PERFORM] the jokes for pg concurrency write performance
  In-Reply-To: <396486431002020743x739a5f80od11dbb83c6e1c399@mail.gmail.com>
  References: <20100202071154.241D94B1C71@mail175-236.sinamail.sina.com.cn> <396486431002020743x739a5f80od11dbb83c6e1c399@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox