On Sun, Jul 6, 2014 at 7:54 AM, Mahesh Narawade
<mahesh.narawade@iqspl.com> wrote:
> We are using your's Postgresql 8.2 database and in that we are facing some
> problem as follows :
>
> - Error : xlog flush request 6A/3B626768 is not satisfied --
> flushed only to 6A/32418FD8
> CONTEXT: writing block 34 of relation 1663/20426/15834.
>
> We need support from your side for solving this error as soon as possible.
8.2 has been unsupported for over 2 years. There are multiple critical
bugs that were fixed in later versions that may be present in 8.2 as
well. Moreover you didn't say which version of Postgres 8.2 you're
running. If you're not running 8.2.23 I suggest you update to 8.2.23
and try again now.
However it looks like this particular error hasn't been seen in widely
since 7.1 which is several years older than 8.2. It shouldn't be a
fatal error, you should be able to use the database as long as you
don't access that corrupted block. Is that what you're observing?
It's not clear what could have caused the corruption, possibly a bug
that has long since been fixed or possibly bad memory or a storage
system that lost synced writes.
--
greg