Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: [ADMIN] ERROR: could not read block
- From: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
- To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
- Cc: Magnus Hagander <mha(at)sollentuna(dot)net>, pgsql-hackers(at)postgresql(dot)org
- Subject: Re: [ADMIN] ERROR: could not read block
- Date: Wed, 30 Nov 2005 16:34:17 -0500 (EST)
- Message-id: <Pine(dot)LNX(dot)4(dot)58(dot)0511301615360(dot)22083(at)eon(dot)cs>
On Wed, 30 Nov 2005, Kevin Grittner wrote: > > I checked with out DBAs, and they are willing to test it. > Thanks, that's very nice! > By they way, they found that they were getting this on a pg_dump, > too. We will test both failure cases. If the test goes OK, we would > be happy to leave it in production with this patch. > I can believe that pg_dump faces the similar situtation, i.e., running out of kernel buffers. But seems pg_dump supports "-Z 0..9" option which uses some external I/O functions from zlib. This part may be not easy to "retry". Magnus, do you want to work on this? If not, I will give it a try. Regards, Qingqing
- Prev by Date: Re: Using multi-row technique with COPY
- Next by Date: Re: Strange interval arithmetic
- Previous by thread: Re: [ADMIN] ERROR: could not read block
- Next by thread: Re: [ADMIN] ERROR: could not read block
- Indexes: