| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: What happens at BIND time? |
| Date: | 2013-08-28 18:44:22 |
| Message-ID: | 521E4506.9060509@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom,
> Does the backend's memory usage climb, or hold steady? If the former,
> I'd bet on client failure to release resources, eg not closing the
> portals when done with them. A memory map from MemoryContextStats
> would help determine exactly what's leaking.
FS cache usage increases through the test run, as you'd expect, but the
amount of pinned memory actually remains pretty much constant -- and has
the same usage in both 8.4 (where the BIND issue doesn't happen) and
9.3b2 (where it does).
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2013-08-28 18:47:47 | Re: ALTER SYSTEM SET command to change postgresql.conf parameters (RE: Proposal for Allow postgresql.conf values to be changed via SQL [review]) |
| Previous Message | Andres Freund | 2013-08-28 18:44:05 | Re: dynamic background workers, round two |