> On Thu, Nov 17, 2005 at 02:04:42PM -0500, Chris Browne wrote:
>> If your OS or disk hardware supports some sort of "snapshotting"
>> technology, so that you can grab a copy of the whole thing as an
>> instant atomic operation, that provides a way to grab a copy while
>> postmaster is running. If
On Thu, Nov 17, 2005 at 02:04:42PM -0500, Chris Browne wrote:
> If your OS or disk hardware supports some sort of "snapshotting"
> technology, so that you can grab a copy of the whole thing as an
> instant atomic operation, that provides a way to grab a copy while
> postmaster is running. If not,
A couple clarifications:
There were only a few network sockets open.
I'm told that the eventlog was reviewed for any events which
mgiht be related to the failures before it was cleared. They
found none, so that makes it fairly certain there was no 2020
event.
-Kevin
>>> "Kevin Grittner" <[EMA
"codeWarrior" <[EMAIL PROTECTED]> writes:
> it doesnt work that way this is postgreSQL -- a relational database.
> you can't just copy the data directory like you can with mySQL or DBase, or
> BTrieve or any of the "old-school" databases... if you need to backup and
> restore data you ne
There weren't a large number of connections -- it seemed to be
that the one big update query, by itself, would do this. It seemed
to get through a lot of rows before failing. This table is normally
"insert only" -- so it would likely be getting most or all of the space
for inserting the updated r
> 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
> >>> Tom Lane <[EMAIL PROTECTED]> >>>
> "Kevin Grittner" <[EMAIL PROTECTED]> writes:
> > None of this seems material, however. It's pretty clear that the
> > problem was exhaustion of the Windows page pool.
> > ...
> > If we don't want to tell Windows users to make highly technical
> > changes
I'm not an expert on that, but it seems reasonable to me that the
page pool would free space as the I/O system caught up with
the load. Also, I'm going on what was said by Qingqing and
in one of the pages he referenced:
http://support.microsoft.com/default.aspx?scid=kb;en-us;274310
-Kevin
>>>
"Kevin Grittner" <[EMAIL PROTECTED]> writes:
> None of this seems material, however. It's pretty clear that the
> problem was exhaustion of the Windows page pool.
> ...
> If we don't want to tell Windows users to make highly technical
> changes to the Windows registry in order to use PostgreSQL,
>
1) We run a couple Java applications on the same box to provide
middle tier access. When the box is heavily loaded, I think I've
seen about 80% PostgreSQL, 20% Java load.
2) I checked that no antivirus software was running, and had the
techs pare down the services running on that box to the absol
it doesnt work that way this is postgreSQL -- a relational database.
you can't just copy the data directory like you can with mySQL or DBase, or
BTrieve or any of the "old-school" databases... if you need to backup and
restore data you need to look at pg_dump and pg_dumpall and the impor
[copying this one over to hackers]
> Our DBAs reviewed the Microsoft documentation you referenced,
> modified the registry, and rebooted the OS. We've been
> beating up on the database without seeing the error so far.
> We'll keep at it for a while.
Very interesting. As this seems to be a re
12 matches
Mail list logo
