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

memory leak in date_part() function in v7.1beta3 ?

From: doj <doj(at)cubic(dot)org>
To: pgsql-bugs(at)postgresql(dot)org
Subject: memory leak in date_part() function in v7.1beta3 ?
Date: 2001-01-27 14:02:05
Message-ID: 3A72D4DD.184EFD80@cubic.org (view raw or flat)
Thread:
Lists: 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

Responses

pgsql-bugs by date

Next:From: Peter MountDate: 2001-01-27 17:01:24
Subject: Re: [BUGS] no way in LargeObject API to detect short read?
Previous:From: Tom LaneDate: 2001-01-27 07:09:21
Subject: Re: Bug with foreign keys and importing from a pg_dump file?

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