pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: zhouqq@cs.toronto.edu
Cc: mha@sollentuna.net
Cc: icub3d@gmail.com
Cc: pgsql-admin@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: [HACKERS] ERROR: could not read block
Date: Thu, 17 Nov 2005 12:51:39 -0500
Message-ID: <29369.1132249899@sss.pgh.pa.us> (raw)
In-Reply-To: <437C6BE802000025000007B7@gwmta.wicourts.gov>
References: <437C6BE802000025000007B7@gwmta.wicourts.gov>

"Kevin Grittner" <Kevin.Grittner@wicourts.gov> 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,
> it does seem wise to use retries, as has already been discussed
> on this thread.

Would a simple retry loop actually help?  It's not clear to me how
persistent such a failure would be.

			regards, tom lane



view thread (41+ messages)  latest in thread

Message-ID: <29369.1132249899@sss.pgh.pa.us>
Permalink:  ../29369.1132249899@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/29369.1132249899@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: tgl@sss.pgh.pa.us, Kevin.Grittner@wicourts.gov, zhouqq@cs.toronto.edu, mha@sollentuna.net, icub3d@gmail.com, pgsql-hackers@postgresql.org
  Subject: Re: [HACKERS] ERROR: could not read block
  In-Reply-To: <29369.1132249899@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox