Skip site navigation (1) Skip section navigation (2)

Re: ERROR: could not read block

From: Kevin Keith <kkeith(at)borderware(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: ERROR: could not read block
Date: 2005-11-15 23:36:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-admin
If I have followed the chain correctly, I saw that you were trying to 
run an update statement on a large number of records in a large table 
right? I have changed my strategy in the past for this type of problem. 
I don't know if it would have fixed this problem or not, but I have seen 
with Postgres and Oracle that updates like this on a large table may 
take very long and cause contention processes.

Anyway, the method I normally use is to write a script that selects the 
records into a cursor and updates one at a time by the primary key, and 
then committing the transaction every so often (i.e. 500 - 1000 
records). This way there will not be the overhead associated with an 
extremely large transaction, and the script will complete much faster (I 
have seen hours vs. minutes).

Hope this helps.


Kevin Grittner wrote:

>I got the error log working on Windows (with redirect_stderr).  I had
>to stop and restart postgres to do so.  I ran the query (for the fourth
>time), and it completed successfully.
>I'm not inclined to believe that changing the redirect_stderr setting
>would change this behavior, so I guess that either it is a
>coincidence or the restart cleared some bad state within postgres.
>Is there anything that anyone wants me to do at this point, to try
>to pin down a cause, or do I drop it here?
>---------------------------(end of broadcast)---------------------------
>TIP 2: Don't 'kill -9' the postmaster

In response to

pgsql-admin by date

Next:From: Qingqing ZhouDate: 2005-11-16 00:07:34
Subject: Re: ERROR: could not read block
Previous:From: Trent ShipleyDate: 2005-11-15 23:27:01
Subject: Re: [ADMIN] Major Problem, need help! Can't run our website!

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group