Re: Frequent Update Project: Design Overview of HOT Updates - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: Frequent Update Project: Design Overview of HOT Updates
Date
Msg-id 2e78013d0611100722n675af139gea5dc6381efe5d10@mail.gmail.com
Whole thread Raw
In response to Re: Frequent Update Project: Design Overview of HOT Updates  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Frequent Update Project: Design Overview of HOT Updates  (NikhilS <nikkhils@gmail.com>)
List pgsql-hackers

On 11/10/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
"Pavan Deolasee" <pavan.deolasee@gmail.com> writes:
> On 11/10/06, Tom Lane <tgl@sss.pgh.pa.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

pgsql-hackers by date:

Previous
From: Gevik Babakhani
Date:
Subject: Protocol specs
Next
From: "Heikki Linnakangas"
Date:
Subject: Re: Protocol specs