memory leak in date_part() function in v7.1beta3 ? - Mailing list pgsql-bugs

From doj
Subject memory leak in date_part() function in v7.1beta3 ?
Date
Msg-id 3A72D4DD.184EFD80@cubic.org
Whole thread Raw
Responses Re: memory leak in date_part() function in v7.1beta3 ?
Re: memory leak in date_part() function in v7.1beta3 ?
List pgsql-bugs
Hello Developers,

at first, thank you for the wonderful work you did on the excellent
database.

I was experimenting with the 7.1beta3 release. When I use the
date_part() function in one query several thousand times (in updates for
example) the postmaster consumes all available memory, until it dies,
with a "no memory left error". If I execute the same queries without
date_part() functions everything runs smooth.

It assume that date_part() has a serious memory leak.

If you like a can reproduce some queries that fail on my machine and
send them to you with a second email.

--
--->
----> doj / cubic
-----> http://www.cubic.org
-----> http://llg.cubic.org

pgsql-bugs by date:

Previous
From: Alex Krohn
Date:
Subject: Re: select fails on indexed varchars.
Next
From: Tom Lane
Date:
Subject: Re: memory leak in date_part() function in v7.1beta3 ?