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 1428BD1E1ED for ; Fri, 26 Mar 2004 02:04:24 +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 80777-10 for ; Thu, 25 Mar 2004 22:04:30 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 22D06D1E0F9 for ; Thu, 25 Mar 2004 22:04:22 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i2Q24RmK017549; Thu, 25 Mar 2004 21:04:27 -0500 (EST) To: josh@agliodbs.com Cc: Stephan Szabo , Qing Zhao , pgsql-performance@postgresql.org Subject: Re: column size too large, is this a bug? In-reply-to: <200403251721.58645.josh@agliodbs.com> References: <082D0538-7E86-11D8-8B9C-000A95AB8896@quotefx.net> <20040325145525.V50544@megazone.bigpanda.com> <16476.1080261565@sss.pgh.pa.us> <200403251721.58645.josh@agliodbs.com> Comments: In-reply-to Josh Berkus message dated "Thu, 25 Mar 2004 17:21:58 -0800" Date: Thu, 25 Mar 2004 21:04:27 -0500 Message-ID: <17548.1080266667@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/370 X-Sequence-Number: 6226 Josh Berkus writes: >> Oh, good eye ... it's that infamous CONNECT BY patch again, without doubt. > Hey, who does this patch? What's wrong wiith it? I'm just venting my annoyance at people expecting us to support hacked-up versions, especially without telling us they're hacked-up. This is the third or fourth trouble report I can recall that was eventually traced to that patch (after considerable effort). Anyway, my guess for the immediate problem is incorrect installation of the patch, viz not doing a complete "make clean" and rebuild after patching. The patch changes the Query struct which is referenced in many more files than are actually modified by the patch, and so if you didn't build with --enable-depend then a simple "make" will leave you with a patchwork of files that have different ideas about the field offsets in Query. I'm a bit surprised it doesn't just dump core... (That's not directly the fault of the patch, though, except to the extent that it can be blamed for coming without adequate installation instructions. What is directly the fault of the patch is that it doesn't force an initdb by changing catversion. The prior trouble reports had to do with views not working because their stored rules were incompatible with the patched backend. We should not have had to deal with that, and neither should those users.) Theory B, of course, is that this is an actual bug in the patch and not just incorrect installation. I'm not interested enough to investigate though. regards, tom lane