| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | "Syed, Rahila" <Rahila(dot)Syed(at)nttdata(dot)com> |
| Cc: | Rahila Syed <rahilasyed90(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
| Subject: | Re: [REVIEW] Re: Compression of full-page-writes |
| Date: | 2015-02-26 08:43:16 |
| Message-ID: | CAHGQGwHd=uaXxfUGUxzxd_z7ogGiqED4B=sxwnQWA=PNxw-D2g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 24, 2015 at 6:46 PM, Syed, Rahila <Rahila(dot)Syed(at)nttdata(dot)com> wrote:
> Hello ,
>
>>I've not read this logic yet, but ISTM there is a bug in that new WAL format because I got the following error and the startup process could not replay any WAL records when I set up replication and enabled wal_compression.
>
>>LOG: record with invalid length at 0/30000B0
>>LOG: record with invalid length at 0/3000518
>>LOG: Invalid block length in record 0/30005A0
>>LOG: Invalid block length in record 0/3000D60 ...
>
> Please fine attached patch which replays WAL records.
Even this patch doesn't work fine. The standby emit the following
error messages.
LOG: invalid block_id 255 at 0/30000B0
LOG: record with invalid length at 0/30017F0
LOG: invalid block_id 255 at 0/3001878
LOG: record with invalid length at 0/30027D0
LOG: record with invalid length at 0/3002E58
...
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2015-02-26 09:09:22 | Re: Partitioning WIP patch |
| Previous Message | Jim Nasby | 2015-02-26 08:30:33 | Re: [HACKERS] Composite index and min() |