--- On Mon, 13/4/09, Greg Smith wrote:
> From: Greg Smith
> Subject: Re: [PERFORM] 2.6.26 kernel and PostgreSQL
> To: "Glyn Astill"
> Cc: pgsql-performance@postgresql.org, "Kevin Grittner"
>
> Date: Monday, 13 April, 2009, 9:25 AM
> On Fri, 10
On Fri, 10 Apr 2009, Glyn Astill wrote:
So it was only for connections over a unix socket, but wow; it's still
an ongoing issue.
The problem is actually with pgbench when running on a UNIX socket, not
with the PostgreSQL server itself. On my tests, the actual database
server itself seems to
--- On Fri, 10/4/09, Kevin Grittner wrote:
> Glyn Astill wrote:
> > I was thinking about shifting my home test machine up
> from 2.6.18,
> > however I recall reading a post somewhere a while back
> about the
> > scheduler in more recent versions being a bit
> cranky...
>
> A recent post o
Glyn Astill wrote:
> I was thinking about shifting my home test machine up from 2.6.18,
> however I recall reading a post somewhere a while back about the
> scheduler in more recent versions being a bit cranky...
A recent post on the topic:
http://archives.postgresql.org/pgsql-performance/200
Hi chaps,
Is anyone using 2.6.26 with postgres? I was thinking about shifting my home
test machine up from 2.6.18, however I recall reading a post somewhere a while
back about the scheduler in more recent versions being a bit cranky...
I just thought I'd ask before I go ahead, I don't have to
