Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial - Mailing list pgsql-hackers

From Stefan Kaltenbrunner
Subject Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial
Date
Msg-id 4B43967C.7000803@kaltenbrunner.cc
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Tom Lane wrote:
> Stefan Kaltenbrunner <stefan@kaltenbrunner.cc> writes:
>> yeah it is probably some strange platform specific issue - however with 
>> some help from the IRC channel I came up with the following patch that
>> considerable reduces the memory bloat (but still needs ~55MB max) and 
>> allows the build to succeed.
> 
> What about Alvaro's idea of adding
> 
>     $row = undef;
> 
> at the bottom of the loop?  That seems marginally less ugly...

not sure I want to argue about the ugliness of perl but that has the 
same effect as my patch so either way would do to get spoonbill green again.

Stefan


pgsql-hackers by date:

Previous
From: Garick Hamlin
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial
Next
From: Robert Haas
Date:
Subject: Re: true serializability and predicate locking