pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: josh@agliodbs.com
Cc: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: Qing Zhao <qzhao@quotefx.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: column size too large, is this a bug?
Date: Thu, 25 Mar 2004 21:04:27 -0500
Message-ID: <17548.1080266667@sss.pgh.pa.us> (raw)
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>

Josh Berkus <josh@agliodbs.com> 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



view thread (22+ messages)  latest in thread

Message-ID: <17548.1080266667@sss.pgh.pa.us>
Permalink:  ../17548.1080266667@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/17548.1080266667@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com, sszabo@megazone.bigpanda.com, qzhao@quotefx.net
  Subject: Re: column size too large, is this a bug?
  In-Reply-To: <17548.1080266667@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox