From: | Thomas Hallgren <thomas(at)tada(dot)se> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Cc: | Eric BOYER <Eric(dot)Boyer(at)insa-toulouse(dot)fr> |
Subject: | refcount leak warnings |
Date: | 2006-06-27 13:55:06 |
Message-ID: | 44A138BA.6050305@tada.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 traced this to the function PrintBufferLeakWarning. AFAICS, it's only
called from the function ResourceOwnerReleaseInternal under the
following comment:
* During a commit, there shouldn't be any remaining pins --- that
* would indicate failure to clean up the executor correctly --- so
* issue warnings. In the abort case, just clean up quietly.
I have no idea where to go from here. What should I look for when trying
to find the cause of such warnings?
Regards,
Thomas Hallgren
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-06-27 13:58:02 | Re: [PATCHES] Non-transactional pg_class, try 2 |
Previous Message | Mark Woodward | 2006-06-27 13:03:55 | Re: vacuum, performance, and MVCC |