Re: folder:lk/lk date:yesterday..

From: Andres Freund <andres(at)2ndquadrant(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: folder:lk/lk date:yesterday..
Date: 2014-04-30 15:41:30
Message-ID: 20140430154130.GD30324@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2014-04-30 17:39:27 +0200, Andres Freund wrote:
> Hi,
>
> Coverity flagged a couple of issues that seem to worth addressing by
> changing the code instead of ignoring them:
>
> 01) heap_xlog_update() looks to coverity as if it could trigger a NULL
> pointer dereference. That's because it thinks that oldtup.t_data is
> NULL if XLR_BKP_BLOCK(0) while reconstructing incremental
> tuples. That fortunately can't happen as incremental updates are
> only performed if the tuples are on the same page.
> Add an Assert().
> 02) Be a bit more consistent in what type to use for a size
> variable. Inconsequential, but more consistent.
> 03) Don't leak memory after connection aborts in pg_recvlogical.
> 04) Use a sensible parameter for memset() when randomizing memory in
> reorderbuffer. Inconsequential.
>
> Could somebody please pick these up?

That might be easier with actual patches...

Greetings,

Andres Freund

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

Attachment Content-Type Size
0001-Assert-that-pre-post-fix-updated-tuples-are-on-the-s.patch text/x-patch 1.1 KB
0002-Use-Size-instead-of-uint32-to-measure-.-size-in-snap.patch text/x-patch 947 bytes
0003-Don-t-leak-memory-after-connection-aborts-in-pg_recv.patch text/x-patch 993 bytes
0004-Pass-sensible-value-to-memset-when-randomizing-reord.patch text/x-patch 1.0 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2014-04-30 15:58:29 Re: Fix initdb for path with whitespace and at char
Previous Message Andres Freund 2014-04-30 15:39:27 folder:lk/lk date:yesterday..