Re: btree_gist valgrind warnings about uninitialized memory

From: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
To: Andres Freund <andres(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: btree_gist valgrind warnings about uninitialized memory
Date: 2014-05-14 11:55:38
Message-ID: 537359BA.4020206@vmware.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 05/13/2014 05:13 PM, Andres Freund wrote:
> That leaves the spgist thing and some infrastructure till we can setup a
> valgrind animal... From what we've caught with it so far that seems
> rather worthwile.
> What's your plans with your spgist fix? Commit it once 9.5 is branched?

Good question. I don't know. I would still like to commit it to 9.4. It
doesn't require catalog changes, but it's an incompatible change in the
WAL record format. If we commit it to 9.4, it means that you cannot
replicate between 9.4beta1 and 9.4beta2. I think that's OK, but how do
others feel about that?

- Heikki

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2014-05-14 12:15:38 Re: popen and pclose redefinitions causing many warning in Windows build
Previous Message Andres Freund 2014-05-14 11:51:46 Re: Sending out a request for more buildfarm animals?