From: | dalgoda(at)ix(dot)netcom(dot)com (Mike Castle) |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Sort memory not being released |
Date: | 2003-06-20 20:28:40 |
Message-ID: | oc7csxh0g.ln2@thune.mrc-home.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In article <20030617212500(dot)GO40542(at)flake(dot)decibel(dot)org>,
Jim C. Nasby <jim(at)nasby(dot)net> wrote:
>Of course I wasn't planning on sucking down a bunch of memory and
>holding on to it. :)
What are you worried about? The unused portions will eventually be paged
out to disk. On the next sort, you'll spend a little less time allocating
the memory (saving time) and a little more time paging the disk in (taking
time). Probably, all in all, you'll end up breaking even.
Just because your process has access to a lot of memory, doesn't mean that
it's all in physical memory at once.
Unless your system ran out of physical memory and/or swap, there shouldn't
be an issue.
It may well be than when you up the sort memory, you may also have to up
swap space. No big deal.
mrc
--
Mike Castle dalgoda(at)ix(dot)netcom(dot)com www.netcom.com/~dalgoda/
We are all of us living in the shadow of Manhattan. -- Watchmen
fatal ("You are in a maze of twisty compiler features, all different"); -- gcc
From | Date | Subject | |
---|---|---|---|
Next Message | Dmitry Tkach | 2003-06-20 20:48:25 | Re: JDBC in PostgreSql for Linux |
Previous Message | Erik Price | 2003-06-20 19:10:01 | Re: JDBC in PostgreSql for Linux |