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

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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
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:31:43
Message-ID: 13739.1262719903@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
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...

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Dave PageDate: 2010-01-05 19:36:20
Subject: Re: libpq naming on Win64
Previous:From: Stefan KaltenbrunnerDate: 2010-01-05 19:23:15
Subject: Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial

pgsql-committers by date

Next:From: Garick HamlinDate: 2010-01-05 19:37:51
Subject: Re: Re: [COMMITTERS] pgsql: Get rid of the need for manual maintenance of the initial
Previous:From: Stefan KaltenbrunnerDate: 2010-01-05 19:23:15
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