Re: WAL replay bugs

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WAL replay bugs
Date: 2014-06-16 03:19:12
Message-ID: CAB7nPqTR8GKth7f6JVwJUGQBempW6MAF0AVT3pG=z_323XU_Xg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Jun 13, 2014 at 4:14 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> A couple of things to note though:
> 1) In order to detect if a page is used for a sequence, SEQ_MAGIC
> needs to be exposed in sequence.h. This is included in the patch
> attached but perhaps this should be changed as a separate patch
> 2) Regression test facility uses some useful parts taken from
> pg_upgrade. I think that we should gather those parts in a common
> place (contrib/common?). This can facilitate the integration of other
> modules using regression based on bash scripts.
> 3) While hacking this facility, I noticed that some ItemId entries in
> btree pages could be inconsistent between master and standby. Those
> items are masked in the current patch, but it looks like a bug of
> Postgres itself.
Attached are 3 patches doing exactly this separation for lisibility.
Regards,
--
Michael

Attachment Content-Type Size
0001-Move-SEQ_MAGIC-to-sequence_h.patch text/plain 1.2 KB
0002-Extract-generic-bash-initialization-process-from-pg_upgrade.patch text/plain 4.6 KB
0003-Buffer-capture-facility-check-WAL-replay-consistency.patch text/plain 39.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2014-06-16 03:56:54 Re: Built-in support for a memory consumption ulimit?
Previous Message Amit Kapila 2014-06-16 03:14:36 Re: postgresql.auto.conf read from wrong directory