| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Zdenek Kotala" <Zdenek(dot)Kotala(at)Sun(dot)COM> |
| Cc: | <pgsql-bugs(at)postgresql(dot)org>, "alex" <an(at)clickware(dot)de> |
| Subject: | Re: Bug (#3484) - Invalid page header again |
| Date: | 2007-12-18 17:42:42 |
| Message-ID: | 87lk7r3nn1.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Zdenek Kotala" <Zdenek(dot)Kotala(at)Sun(dot)COM> writes:
> I got dump of affected two blocks from Alex and it seems that both blocks were
> overwritten together with some 128bytes length structure (there some pattern)
> and complete damaged size is 9728bytes (first block is overwritten completely
> and second one only at the beginning), but another buffer from another relation
> could be overwritten too.
I don't understand this 9728 bytes. Postgres blocks are 8192 bytes. Are you
saying one whole block is trashed and then part, but not all, of the next
block?
What's the block size of the ZFS filesystem? And what exactly does the trash
data look like?
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Ask me about EnterpriseDB's On-Demand Production Tuning
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-12-18 19:08:33 | Re: Bug (#3484) - Invalid page header again |
| Previous Message | Gregory Stark | 2007-12-18 17:38:56 | Re: BUG #3824: Query hangs when result set empty using sort and limit |