X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id C53F19DCA30 for ; Mon, 9 Jan 2006 16:26:29 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 34198-02 for ; Mon, 9 Jan 2006 16:26:29 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from flake.decibel.org (unknown [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 6BA0D9DC9F2 for ; Mon, 9 Jan 2006 16:26:25 -0400 (AST) Received: by flake.decibel.org (Postfix, from userid 1001) id 9D2F439841; Mon, 9 Jan 2006 14:26:26 -0600 (CST) Date: Mon, 9 Jan 2006 14:26:26 -0600 From: "Jim C. Nasby" To: Tsirkin Evgeny Cc: Tsirkin Evgeny , pgsql-admin@postgresql.org Subject: Re: preventing deadlocks Message-ID: <20060109202626.GN3902@pervasive.com> References: <20051228202607.GA5194@wolff.to> <20060104003001.GY82560@pervasive.com> <20060105065747.GA17322@wolff.to> <43BCDA17.6070806@mail.jct.ac.il> <20060105084030.GA32572@wolff.to> <43BCDE94.3030902@mail.jct.ac.il> <20060105210210.GX43311@pervasive.com> <43C0D3F1.1090306@mail.jct.ac.il> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43C0D3F1.1090306@mail.jct.ac.il> X-Operating-System: FreeBSD 6.0-RELEASE amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.081 required=5 tests=[AWL=0.081] X-Spam-Score: 0.081 X-Spam-Level: X-Archive-Number: 200601/98 X-Sequence-Number: 20186 On Sun, Jan 08, 2006 at 10:57:21AM +0200, Tsirkin Evgeny wrote: > > Jim C. Nasby wrote: > > >Personally, I'd just put the effort into setting up the insert/delete > >stuff and a means to periodically roll that info up into a summary > >table. I know that this has come up in the past, so you can probably > >find someone else who's already done this and might be able to provide > >you with code. Even if you have to write it from scratch, I doubt it's > >more work than what you've already put into trying to get the other > >scheme to work. > > > Thanks.Do you think that using LISTEN/NOTIFY mechanism for rolling up > the summary table > could be used? Sure, although on a busy system it might be better to just poll once a minute or so. I'm not sure what the overhead for a NOTIFY is, but I imagine it would start to add up if you were calling several times a second. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461