A couple logical decoding fixes/patches

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: A couple logical decoding fixes/patches
Date: 2014-05-08 16:29:00
Message-ID: 20140508162900.GA5556@awork2.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

Patch 01: Fix a couple of embarassing typos. Most of them harmless, but
one isn't and can lead to crashing or decoding wrong data.

Patch 02: Don't crash with an Assert() failure if wal_level=logical but
max_replication_slots=0.

Patch 03: Add valgrind suppression for writing out padding bytes. That's
better than zeroing the data from the get go because unitialized
accesses are still detected.

Details are in the commit messages of the individual patches.

Greetings,

Andres Freund

--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

Attachment Content-Type Size
0001-Fix-a-couple-of-brown-paper-bag-typos-in-the-logical.patch text/x-patch 4.1 KB
0002-Remove-overeager-assertion-in-wal_level-logical-spec.patch text/x-patch 957 bytes
0003-Add-valgrind-suppression-to-ignore-padding-bytes-in-.patch text/x-patch 835 bytes

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message andres 2014-05-08 16:33:55 [PATCH] Fix harmless access to uninitialized memory in ri_triggers.c.
Previous Message Robert Haas 2014-05-08 16:27:16 Re: PQputCopyEnd doesn't adhere to its API contract