| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Thomas Hallgren <thomas(at)tada(dot)se> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Eric BOYER <Eric(dot)Boyer(at)insa-toulouse(dot)fr> |
| Subject: | Re: refcount leak warnings |
| Date: | 2006-06-27 14:08:52 |
| Message-ID: | 20060627140852.GB16840@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 27, 2006 at 03:55:06PM +0200, Thomas Hallgren wrote:
> I have a PL/Java user that performs some lengthy operations. Eventually,
> he get warnings like:
>
> WARNING: buffer refcount leak: [779] (rel=1663/16440/52989, blockNum=3,
> flags=0x27, refcount=1 2)
I think the comment about failing to clean up is correct. AIUI, if
you've done a heap_open without a heap_close, or an index_open without
an index_close, you'll get warnings like this. Maybe using SPI without
clearing everything.
Obviously something didn't get cleaned up somewhere, but what? Maybe
identifying the rel and looking at that block might help identify the
issue.
Have a ncie day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-06-27 14:12:38 | Re: refcount leak warnings |
| Previous Message | Tom Lane | 2006-06-27 13:58:02 | Re: [PATCHES] Non-transactional pg_class, try 2 |