From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>, <zhouqq(at)cs(dot)toronto(dot)edu> |
Cc: | <icub3d(at)gmail(dot)com>, <pgsql-admin(at)postgresql(dot)org>, <pgsql-hackers(at)postgresql(dot)org>, <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: [HACKERS] ERROR: could not read block |
Date: | 2005-11-17 19:05:34 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE92E86F@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-hackers |
> None of this seems material, however. It's pretty clear that
> the problem was exhaustion of the Windows page pool. Our
> Windows experts have reconfigured the machine (which had been
> tuned for Sybase ASE). Their changes have boosted the page
> pool from 20,000 entries to 180,000 entries. We're
> continuing to test to ensure that the problem is not showing
> up with this configuration; but, so far, it looks good.
Nope, with these numbers it doesn't. I was looking for a reason as to
why it would exhaust the pool - such as a huge number of connections.
Which doesn't appear to be so :-(
Another thing that will affect this is if you have a lot of network
sockets open. Anything like that?
BTW; do you get any eventid 2020 in your eventlog?
> If we don't want to tell Windows users to make highly
> technical changes to the Windows registry in order to use
> PostgreSQL, it does seem wise to use retries, as has already
> been discussed on this thread.
Yeah, I think it's at least worth a try at that.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Grittner | 2005-11-17 19:54:03 | Re: [HACKERS] ERROR: could not read block |
Previous Message | Chris Browne | 2005-11-17 19:04:42 | Re: restore challenge |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2005-11-17 19:28:10 | Improving count(*) |
Previous Message | Magnus Hagander | 2005-11-17 18:56:21 | Re: [HACKERS] ERROR: could not read block |