X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id AB642D1EBAB for ; Fri, 26 Mar 2004 18:02:21 +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 93218-08 for ; Fri, 26 Mar 2004 14:02:25 -0400 (AST) Received: from davinci.ethosmedia.com (server228.ethosmedia.com [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id 34856D1BA75 for ; Fri, 26 Mar 2004 14:02:18 -0400 (AST) Received: from [63.195.55.98] (HELO 192.168.1.29) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 4700314; Fri, 26 Mar 2004 10:03:41 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions To: Qing Zhao , Tom Lane Subject: Re: column size too large, is this a bug? Date: Fri, 26 Mar 2004 10:01:47 -0800 User-Agent: KMail/1.5.4 Cc: pgsql-performance@postgresql.org, Stephan Szabo References: <082D0538-7E86-11D8-8B9C-000A95AB8896@quotefx.net> <17548.1080266667@sss.pgh.pa.us> <1DA4E1C7-7F4B-11D8-8D3D-000A95AB8896@quotefx.net> In-Reply-To: <1DA4E1C7-7F4B-11D8-8D3D-000A95AB8896@quotefx.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200403261001.47665.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/377 X-Sequence-Number: 6233 Quig, > Your responses have made it much clear for us. BTW, do you > think that it's better for us just to rewrite everything so we don't > need to use the patch at all? Why do others still use it? Others use it because of the same reason you do. If you want to use the patch for seemless porting, I suggest that you contact Evgen directly. He's not very active on the main project mailing lists, so you'll need to e-mail him personally. You may also need to sponsor him for bug fixes, since he is apparently an independent developer. I don't really know him. As an alternative, you may want to take a look at the IS_CONNECTED_BY patch in /contrib/tablefunc in the PostgreSQL source. As this was developed by Joe Conway, who is a very active major contributor in the community, it is more likely to be bug-free. However, it will force you to change your query syntax somewhat. Of course, there are other query tree structures you could use if you're willing to modify your database design. But you may not want to go that far. -- -Josh Berkus Aglio Database Solutions San Francisco