Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f8INQmd89886 for ; Tue, 18 Sep 2001 19:26:50 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f8INQHK26480; Tue, 18 Sep 2001 19:26:17 -0400 (EDT) To: darcy@druid.net (D'Arcy J.M. Cain) cc: jdiehl@sandia.gov (Diehl Jeffrey), pgsql-sql@postgresql.org (''pgsql-sql@postgresql.org' ') Subject: Re: Out of free buffers... HELP! In-reply-to: <20010918112236.2E90F1A6F@druid.net> References: <20010918112236.2E90F1A6F@druid.net> Comments: In-reply-to darcy@druid.net (D'Arcy J.M. Cain) message dated "Tue, 18 Sep 2001 07:22:36 -0400" Date: Tue, 18 Sep 2001 19:26:16 -0400 Message-ID: <26477.1000855576@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200109/130 X-Sequence-Number: 4802 darcy@druid.net (D'Arcy J.M. Cain) writes: > Thus spake Diehl, Jeffrey >> psql ids -c 'select src,dst,count(*) from brick* where src_port=135 >> group by src,dst' > /tmp/135.dat > Hard to tell without knowing more but perhaps you need another table > instead of/in addition to this one that just tracks the counts. You > can use a trigger to increment it. If you only allow inserts this > should be easy. Deletes are easy too. Updates are a little trickier. The thing is, you shouldn't ever get "out of free buffers", period. Jeffrey must be running into some kind of buffer-leak bug ... but it's hard to think what, unless he's running an extremely old PG version. We haven't seen reports of buffer leaks in a long time. So I'd like to run that down, quite independently of whether he should change his query for efficiency. regards, tom lane