From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | josh(at)agliodbs(dot)com, pgsql-hackers(at)postgresql(dot)org, "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
Subject: | Re: Frequent Update Project: Design Overview of HOT Updates |
Date: | 2006-11-10 15:22:36 |
Message-ID: | 2e78013d0611100722n675af139gea5dc6381efe5d10@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 11/10/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> writes:
> > On 11/10/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > (2) Isn't this full of race conditions?
>
> > I agree, there could be race conditions. But IMO we can handle those.
>
> Doubtless you can prevent races by introducing a bunch of additional
> locking. The question was really directed to how much concurrent
> performance is left, once you get done locking it down.
>
>
I understand your point and I can clearly see a chance to improve upon the
current
locking implementation in the prototype even though we are seeing a good
performance
boost for 50 clients and 50 scaling factor with pgbench runs as mentioned by
Nikhil.
Regards,
Pavan
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2006-11-10 15:25:44 | Re: Protocol specs |
Previous Message | Andrew Dunstan | 2006-11-10 15:18:05 | Re: how & from where to start & admin pgsql on red hat |