Thread: Re: 回复:Re: [PERFORM] the jokes for pg concurrency write performance

From:
Richard Broersma
Date:

2010/2/1  <>:

> 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  mailing is
included.


--
Regards,
Richard Broersma Jr.

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

From:
Tom Lane
Date:

Richard Broersma <> writes:
> 2010/2/1  <>:
>> 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?

Hmmm ... I gave a talk by that name at OSCON.

In 2002.

            regards, tom lane