| From: | Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> |
|---|---|
| To: | luben karavelov <karavelov(at)mail(dot)bg> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #6763: Severe memory leak with arrays and hstore |
| Date: | 2012-07-27 05:59:25 |
| Message-ID: | 50122E3D.4050208@ringerc.id.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 07/27/2012 10:31 AM, Craig Ringer wrote:
> Ouch. Sure looks like a leak to me, yeah.
... but it turns out I'm not thinking very straight. I forgot to check
the size of your `shared_buffers' or `work_mem' and forgot to get you to
report `free -m' output after each run to measure _real_ memory use.
During testing I did got a backend crash when running an INSERT - which
I didn't expect given that I have only 20MB of work_mem and 256MB of
shared_buffers. I was surprised by that as I would not have expected
that query to require a huge gob of RAM. I didn't dig much further as
I'm on a swapless system with overcommit enabled ( 'cos the Java VM
does't work with overcommit off ) which isn't exactly a recommended Pg
configuration.
--
Craig Ringer
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jez Wain | 2012-07-27 09:53:16 | Re: BUG #6760: make check fails on strings SQL T581 regex test |
| Previous Message | Craig Ringer | 2012-07-27 05:52:29 | Re: BUG #6763: Severe memory leak with arrays and hstore |