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 1DFE89DCAE5 for ; Sun, 8 Jan 2006 04:48:39 -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 88366-03 for ; Sun, 8 Jan 2006 04:48:39 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail3.cc.huji.ac.il (mail3.cc.huji.ac.il [132.64.1.21]) by postgresql.org (Postfix) with ESMTP id C6F1C9DC879 for ; Sun, 8 Jan 2006 04:48:36 -0400 (AST) Received: from mail3.cc.huji.ac.il (localhost [127.0.0.1]) by mail3.cc.huji.ac.il (Postfix) with SMTP id EA36C15E372; Sun, 8 Jan 2006 10:46:12 +0200 (IST) Received: by mail3.cc.huji.ac.il (Postfix, from userid 31998) id DEC3A15E424; Sun, 8 Jan 2006 10:46:12 +0200 (IST) Received: from [132.64.52.127] (evegeni.mm.huji.ac.il [132.64.52.127]) by mail3.cc.huji.ac.il (Postfix) with ESMTP id 9938815E372; Sun, 8 Jan 2006 10:46:10 +0200 (IST) Message-ID: <43C0D3F1.1090306@mail.jct.ac.il> Date: Sun, 08 Jan 2006 10:57:21 +0200 From: Tsirkin Evgeny User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Jim C. Nasby" CC: Tsirkin Evgeny , pgsql-admin@postgresql.org Subject: Re: preventing deadlocks References: <43B10E07.7010503@mail.jct.ac.il> <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> In-Reply-To: <20060105210210.GX43311@pervasive.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus: scanned by VAMS 2005 version 8.1024 from Sat Jan 7 13:57:41 2006 CET X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.286 required=5 tests=[AWL=0.286] X-Spam-Score: 0.286 X-Spam-Level: X-Archive-Number: 200601/89 X-Sequence-Number: 20177 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?