From: | Richard Broersma <richard(dot)broersma(at)gmail(dot)com> |
---|---|
To: | wyx6fox(at)sina(dot)com, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: 回复:Re: [PERFORM] the jokes for pg concurrency write performance |
Date: | 2010-02-02 15:43:52 |
Message-ID: | 396486431002020743x739a5f80od11dbb83c6e1c399@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
2010/2/1 <wyx6fox(at)sina(dot)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(at)postgresql(dot)org mailing is
included.
--
Regards,
Richard Broersma Jr.
Visit the Los Angeles PostgreSQL Users Group (LAPUG)
http://pugs.postgresql.org/lapug
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2010-02-02 16:08:53 | Re: use pgsql in a big project, but i found pg has some big problem on concurrency write operation, maybe a joke for myself ! |
Previous Message | Edgardo Portal | 2010-02-02 13:06:46 | Re: Slow-ish Query Needs Some Love |