Skip site navigation (1) Skip section navigation (2)

Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial

From: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial
Date: 2010-01-05 19:43:56
Message-ID: 4B43967C.7000803@kaltenbrunner.cc (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
Tom Lane wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)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

In response to

Responses

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-01-05 19:46:17
Subject: Re: true serializability and predicate locking
Previous:From: Tom LaneDate: 2010-01-05 19:42:03
Subject: Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial

pgsql-committers by date

Next:From: Tom LaneDate: 2010-01-05 20:23:32
Subject: pgsql: Fix genbki.pl and Gen_fmgrtab.pl to use PID-specific temp file
Previous:From: Tom LaneDate: 2010-01-05 19:42:03
Subject: Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group