Re: Optimizing Read-Only Scalability

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Optimizing Read-Only Scalability
Date: 2009-05-15 08:30:59
Message-ID: 1242376259.3843.618.camel@ebony.2ndQuadrant
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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.com
PostgreSQL Training, Services and Support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-05-15 09:43:54 Re: New trigger option of pg_standby
Previous Message Heikki Linnakangas 2009-05-15 06:06:48 Re: pgsql: Add recovery_end_command option to recovery.conf.