Re: [HACKERS] lock failed and buffer leak

Peter T Mount <psqlhack@maidast.demon.co.uk>

From: Peter T Mount <psqlhack@maidast.demon.co.uk>
To: Claudiu Balciza <altex@decebal.ro>
Cc: pgsql questions <pgsql-questions@hub.org>, pgsql hackers <pgsql-hackers@hub.org>
Date: 1998-04-18T10:37:07Z
Lists: pgsql-hackers
On Fri, 17 Apr 1998, SC Altex Impex SRL wrote:

> testing the (postgresql 6.3.1 included) jdbc ImageViewer example.
> It works. No errors.
> But in the pgsql log I fond these (actually many more):
> ----------------------------------------------------------------------------
> -----------
> Apr 17 10:08:02 digital logger: NOTICE:  DateStyle is Postgres with US
> (NonEuropean) conventions

This one is caused by the driver finding out what datestyle is in use.
This is normal.

> Apr 17 10:08:07 digital logger: NOTICE:  buffer leak [65] detected in
> BufferPoolCheckLeak()
> Apr 17 10:08:07 digital logger: NOTICE:  LockRelease: locktable lookup
> failed, no lock
> Apr 17 10:08:07 digital logger: NOTICE:  buffer leak [75] detected in
> BufferPoolCheckLeak()
> Apr 17 10:08:08 digital logger: NOTICE:  LockRelease: locktable lookup
> failed, no lock
> Apr 17 10:08:47 digital logger: NOTICE:  buffer leak [65] detected in
> BufferPoolCheckLeak()

These are caused by the large object api in the backend. I'm not sure
where these are caused by, but when I was fixing that part of the backend
(to get it working for JDBC), I couldn't see it.

[Hackers: any ideas?]

-- 
Peter T Mount  petermount@earthling.net or pmount@maidast.demon.co.uk
Main Homepage: http://www.demon.co.uk/finder
Work Homepage: http://www.maidstone.gov.uk Work EMail: peter@maidstone.gov.uk