| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Gold <jgold(at)mazunetworks(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org, Joe Maldonado <joe(at)mazunetworks(dot)com> |
| Subject: | Re: Postmaster Out of Memory |
| Date: | 2005-06-28 05:18:06 |
| Message-ID: | 10747.1119935886@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Jeff Gold <jgold(at)mazunetworks(dot)com> writes:
> Tom Lane wrote:
>> TRUNCATE and CLUSTER both rebuild indexes, so they'd also trigger the
>> leak.
> Sorry to bug you again, but I have two quick followup questions: (1) is
> the leak you discovered fixed on the 8.0 branch? and (2) would closing
> the database connection once per day be a reasonable way to work around
> the problem in the absence of the patch you forwarded?
It is fixed in CVS-tip of all branches back to 7.3, but there is not any
release yet incorporating the fix. Yes, closing your session and
starting a fresh one is a usable workaround.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-06-28 05:40:32 | Re: DANGER Windows version might hurt you |
| Previous Message | Jim C. Nasby | 2005-06-28 01:55:06 | Re: Populating huge tables each day |