Guy Thornley <[EMAIL PROTECTED]> writes:
>> That's what I'd expect if this scenario applies:
>> the pages will be fixed by WAL recovery, it's just that the recently
>> added check for broken page headers was interfering :-(
> What I don't grok is why all the affected files were indexes, and none
>
> > PANIC: invalid page header in block 6 of relation "17792"
> > This was on postgres 7.4.
>
> I believe this is fixed in 7.4.1:
...
> And no sign of corruption after you'd run through the recovery with
> zero_damaged_pages?
I checked them this morning; there isnt.
Sorry for bugging you abou
Hi Michael,
Are you able to figure out why the thread-safety flag would
trigger this ecpg failure with dyntest.pgc ?
Thanks.
Gan
At 3:40 pm +0800 2004/1/5, Liang, Guang Yu (Lucy) wrote:
Hi, Michael,
When configure without enable-thread-safety, the example
works perfect. Thank you for the great
Hello,
org.postgresql.jdbc1.AbstractJdbc1Statement.setBinaryStream()
in postgresql 7.4.1 wrongly assumes, that
java.io.InputStream.read(byte[] b,int offset,int len )
will always read len bytes. InputStream only guarantees to
return at least 1 byte per call. The attached patch solves the bug.
Btw
Guy Thornley <[EMAIL PROTECTED]> writes:
> On one of our test boxen here, weve experienced a corrupted file during
> database recovery after box power outage. The specific error message is
> PANIC: invalid page header in block 6 of relation "17792"
> This was on postgres 7.4.
I believe this
The following bug has been logged online:
Bug reference: 1043
Logged by: Serkan SUNEL
Email address: [EMAIL PROTECTED]
PostgreSQL version: 7.4
Operating system: Windows XP
Description:PSQL.exe
Details:
Problem occur while restoring the database from the backup
Hi,
On one of our test boxen here, weve experienced a corrupted file during
database recovery after box power outage. The specific error message is
PANIC: invalid page header in block 6 of relation "17792"
At this point I fired up a hex dumper to inspect the file, and the last
block in t
