X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (neptune.hub.org [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id BBEEBD1B43F for ; Fri, 5 Dec 2003 16:53:26 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 86410-01 for ; Fri, 5 Dec 2003 12:52:55 -0400 (AST) Received: from uhh.alcaron.ee (uhh.alcaron.ee [194.204.62.169]) by svr1.postgresql.org (Postfix) with ESMTP id 85074D1B445 for ; Fri, 5 Dec 2003 12:52:54 -0400 (AST) Received: from iff by uhh.alcaron.ee with local id 1ASJCH-0007xz-00; Fri, 05 Dec 2003 18:52:53 +0200 Date: Fri, 5 Dec 2003 18:52:53 +0200 To: pgsql-performance@postgresql.org Subject: Re: Slow UPADTE, compared to INSERT Message-ID: <20031205165253.GB30510@alcaron.ee> References: <20031204185751.GA15893@alcaron.ee> <20031205014514.GA21079@alcaron.ee> <20031205020728.GA21440@alcaron.ee> <200312051008.20317.dev@archonet.com> <20031205123843.GA27170@alcaron.ee> <3FD07EEA.8030007@persistent.co.in> <20031205131325.GB27524@alcaron.ee> <3FD08D6A.4080207@persistent.co.in> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FD08D6A.4080207@persistent.co.in> User-Agent: Mutt/1.3.28i From: Ivar Zarans X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200312/128 X-Sequence-Number: 4988 On Fri, Dec 05, 2003 at 07:21:38PM +0530, Shridhar Daithankar wrote: > planner consider seemingly same type as different. e.g. treating int8 as > different than int4. Obvious thinking is they should be same. But given > postgresql's flexibility with create type, it is difficult to promote. OK, this makes sense and explains a lot. Thanks! > Well, then pypgsql should be upgraded to query the pg catalogd to find > exact type of column. But that would be too cumbersome I guess. Yes, so it seems. Time to rewrite my queries :) Thanks again for help and explanations! -- Ivar