From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Nathan Barnett" <nbarnett(at)cellularphones(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Memory Usage |
Date: | 2000-12-08 16:07:51 |
Message-ID: | 739.976291671@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Nathan Barnett" <nbarnett(at)cellularphones(dot)com> writes:
> I am having a small issue with PostgreSQL 7.0.3 on FreeBSD 4.2 Stable. When
> I perform an update on a table with roughly 2 million rows, the postgres
> process starts eating up memory until it eventually uses up all of the
> memory and exits without finishing. I have also seen the same thing happen
> in complex SELECT statements that I have run. The update statement is as
> follows:
> UPDATE pages SET createdtime = NOW();
The now() function invocation leaks memory --- only a dozen or two bytes
per invocation, I think, but it'll still add up over that many rows.
You'd see the same sort of problem with function calls or operations on
any pass-by-reference datatype.
This is fixed for 7.1...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | The Hermit Hacker | 2000-12-08 16:19:56 | Re: Indexing for geographic objects? |
Previous Message | Nathan Barnett | 2000-12-08 16:03:18 | Memory Usage |