Re: Optimizing Read-Only Scalability - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Optimizing Read-Only Scalability
Date
Msg-id 1242376259.3843.618.camel@ebony.2ndQuadrant
Whole thread Raw
In response to Re: Optimizing Read-Only Scalability  (Josh Berkus <josh@agliodbs.com>)
Responses Re: Optimizing Read-Only Scalability  ("Jignesh K. Shah" <J.K.Shah@Sun.COM>)
List pgsql-hackers
On Thu, 2009-05-14 at 16:21 -0700, Josh Berkus wrote:

> > So we can optimize away the scan through the procarray by doing two "if"
> > tests, one outside of the lock, one inside. In normal running, both will
> > be optimized away, though in read-only periods we would avoid much work.
> 
> How much work would it be to work up a test patch?

Not much. The most important thing is a place to test it and access to
detailed feedback. Let's see if Dimitri does this.

There are some other tuning aspects to be got right first also, but
those are already known.

-- Simon Riggs           www.2ndQuadrant.comPostgreSQL Training, Services and Support



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [COMMITTERS] pgsql: Add recovery_end_command option to recovery.conf.
Next
From: Simon Riggs
Date:
Subject: Re: New trigger option of pg_standby