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 91C989DCAE5 for ; Thu, 5 Jan 2006 04:51:51 -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 30215-02 for ; Thu, 5 Jan 2006 04:51:52 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from mail1.cc.huji.ac.il (mail1.cc.huji.ac.il [132.64.1.17]) by postgresql.org (Postfix) with ESMTP id B58719DCADB for ; Thu, 5 Jan 2006 04:51:48 -0400 (AST) Received: from mail1.cc.huji.ac.il (localhost [127.0.0.1]) by mail1.cc.huji.ac.il (Postfix) with SMTP id A7844417333; Thu, 5 Jan 2006 10:51:47 +0200 (IST) Received: by mail1.cc.huji.ac.il (Postfix, from userid 31998) id 3C317417640; Thu, 5 Jan 2006 10:45:03 +0200 (IST) Received: from [132.64.52.127] (evegeni.mm.huji.ac.il [132.64.52.127]) by mail1.cc.huji.ac.il (Postfix) with ESMTP id 9022B417CEB; Thu, 5 Jan 2006 10:44:57 +0200 (IST) Message-ID: <43BCDE94.3030902@mail.jct.ac.il> Date: Thu, 05 Jan 2006 10:53:40 +0200 From: Tsirkin Evgeny User-Agent: Mozilla Thunderbird 1.0.7 (Windows/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Bruno Wolff III Cc: 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> In-Reply-To: <20060105084030.GA32572@wolff.to> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus: scanned by VAMS 2005 version 8.1020 from Wed Jan 4 15:56:09 2006 CET X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.342 required=5 tests=[AWL=0.342] X-Spam-Score: 0.342 X-Spam-Level: X-Archive-Number: 200601/66 X-Sequence-Number: 20154 Bruno,thanks for the answer but this was not at ALL that i asked. Neither mind . Note however, how polite i am . Thanks anyway. Evgeny Bruno Wolff III wrote: >On Thu, Jan 05, 2006 at 10:34:31 +0200, > Tsirkin Evgeny wrote: > > >>I understand THAT ,I meant why int will give me more performance. >> >> > >Because if you have a bunch of processes sitting around waiting for table >locks, the average time to process queries will be higher. If you are >already limited by IO throughput or CPU usage this may not be a big deal, >but in many cases it will be. > > > >>Well i DO have a lot of concurrent queries,that is the whole point. >> >> > >Then you probably want to do what people have been recommending you do. > > > >>That does not help me .What i want is : >>select 1 from table a where whatever for update; >>issuing this should fire a trigger that does: >> >> > >You can't trigger on select statements. So this approach won't workin any case. > > > >>select 1 from table counter where a.pkey=counter.ident or something >>however this should only be done for select FOR UPDATE! >>And i can't know that inside the trigger! >> >> > >---------------------------(end of broadcast)--------------------------- >TIP 1: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly > >