agora inbox for postgres@postgres.berkeley.edu
help / color / mirror / Atom feedbuffer leak detected in BufferPoolCheckLeak()
3+ messages / 3 participants
[nested] [flat]
* buffer leak detected in BufferPoolCheckLeak()
@ 1994-08-01 11:19 Wojtek Bogusz <Wojtek.Bogusz@fuw.edu.pl>
1994-08-03 18:28 ` Re: buffer leak detected in BufferPoolCheckLeak() Kai Petzke <wpp@marie.physik.tu-berlin.de>
0 siblings, 1 reply; 3+ messages in thread
From: Wojtek Bogusz @ 1994-08-01 11:19 UTC (permalink / raw)
To: legacy
Hello,
I am defining new types for PG. First I define IO and types and then
relation functions and on the end operators. While defining operators I
get strange NOTICE messages:
...
Query sent to backend is "define operator << ( arg1 = nlschar, arg2 = nlschar, procedure = nlschar_lt, associativity = left, restrict = intltsel, join = intltjoinsel) "
DEFINE
Query sent to backend is "define operator >> ( arg1 = nlschar, arg2 = nlschar, procedure = nlschar_gt, associativity = left, commutator = <<, restrict = intltsel, join = intltjoinsel) "
NOTICE:Aug 1 12:58:26:buffer leak detected in BufferPoolCheckLeak()
NOTICE:Aug 1 12:58:26:[00] (freeNext=18, freePrev=19, relname=pg_operator, blockNum=2, flags=0x14, refcount=0 0)
NOTICE:Aug 1 12:58:26:[01] (freeNext=47, freePrev=7, relname=pg_log, blockNum=0, flags=0x14, refcount=0 0)
... much more NOTICE:
NOTICE:Aug 1 12:58:27:[63] (freeNext=15, freePrev=54, relname=pg_procnameind, blockNum=3, flags=0x14, refcount=0 0)
DEFINE
This happens on definition each second operator. What does it mean ?
Does I am making any thing wrong ?
Thank You
Wojtek
==============================================================================
To add/remove yourself to/from the POSTGRES mailing list: send mail with
the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"
If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
a human will deal with it. DO NOT post to the "postgres" mailing list.
==============================================================================
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: buffer leak detected in BufferPoolCheckLeak()
1994-08-01 11:19 buffer leak detected in BufferPoolCheckLeak() Wojtek Bogusz <Wojtek.Bogusz@fuw.edu.pl>
@ 1994-08-03 18:28 ` Kai Petzke <wpp@marie.physik.tu-berlin.de>
1994-08-04 19:23 ` Re: buffer leak detected in BufferPoolCheckLeak() Paul M. Aoki <aoki@CS.Berkeley.EDU>
0 siblings, 1 reply; 3+ messages in thread
From: Kai Petzke @ 1994-08-03 18:28 UTC (permalink / raw)
To: Wojtek Bogusz <Wojtek.Bogusz@fuw.edu.pl>; +Cc: legacy
Hi,
The "buffer leak" notices seem to be caused by an internal problem of
postgres, not by the user. I have gotton a bunch of these notices once,
when I ran the regression test, but could not reproduce the problem.
The problem was not reproducable, though. If anybody has a set of
queries, which reproducably produce a buffer leak, I would appreciate,
if you send me them.
Kai
==============================================================================
To add/remove yourself to/from the POSTGRES mailing list: send mail with
the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"
If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
a human will deal with it. DO NOT post to the "postgres" mailing list.
==============================================================================
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: buffer leak detected in BufferPoolCheckLeak()
1994-08-01 11:19 buffer leak detected in BufferPoolCheckLeak() Wojtek Bogusz <Wojtek.Bogusz@fuw.edu.pl>
1994-08-03 18:28 ` Re: buffer leak detected in BufferPoolCheckLeak() Kai Petzke <wpp@marie.physik.tu-berlin.de>
@ 1994-08-04 19:23 ` Paul M. Aoki <aoki@CS.Berkeley.EDU>
0 siblings, 0 replies; 3+ messages in thread
From: Paul M. Aoki @ 1994-08-04 19:23 UTC (permalink / raw)
To: Kai Petzke <wpp@marie.physik.tu-berlin.de>; +Cc: Wojtek Bogusz <Wojtek.Bogusz@fuw.edu.pl>; legacy
wpp@marie.physik.tu-berlin.de (Kai Petzke) writes:
> The "buffer leak" notices seem to be caused by an internal problem of
> postgres, not by the user.
yes. a piece of code is pinning a buffer somewhere and then neglecting
to unpin it again. the scary notices were added to facilitate debugging.
i thought the define operator one had been fixed. maybe not. there is a
new one lurking in the btree code somewhere..
--
Paul M. Aoki | University of California at Berkeley
aoki@CS.Berkeley.EDU | Dept. of EECS, Computer Science Division (#1776)
| Berkeley, CA 94720-1776
==============================================================================
To add/remove yourself to/from the POSTGRES mailing list: send mail with
the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU"
If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
a human will deal with it. DO NOT post to the "postgres" mailing list.
==============================================================================
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~1994-08-04 19:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1994-08-01 11:19 buffer leak detected in BufferPoolCheckLeak() Wojtek Bogusz <Wojtek.Bogusz@fuw.edu.pl>
1994-08-03 18:28 ` Kai Petzke <wpp@marie.physik.tu-berlin.de>
1994-08-04 19:23 ` Paul M. Aoki <aoki@CS.Berkeley.EDU>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox