Re: [HACKERS] lock failed and buffer leak - Mailing list pgsql-hackers

From Peter T Mount
Subject Re: [HACKERS] lock failed and buffer leak
Date
Msg-id Pine.LNX.3.95.980418113451.7910B-100000@maidast.demon.co.uk
Whole thread Raw
In response to lock failed and buffer leak  ("SC Altex Impex SRL" <office.Altex@decebal.ro>)
List 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


pgsql-hackers by date:

Previous
From: Peter T Mount
Date:
Subject: Re: [HACKERS] Proposal for async support in libpq
Next
From: Peter T Mount
Date:
Subject: Re: [HACKERS] Proposal for async support in libpq