BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data

From: "Marcello Ceschia" <Marcello(dot)Ceschia(at)medizin(dot)uni-leipzig(dot)de>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data
Date: 2008-03-31 12:26:54
Message-ID: 200803311226.m2VCQskW015483@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches


The following bug has been logged online:

Bug reference: 4070
Logged by: Marcello Ceschia
Email address: Marcello(dot)Ceschia(at)medizin(dot)uni-leipzig(dot)de
PostgreSQL version: 8.2.5 and 8.3.0
Operating system: Windows XP
Description: Join more then ~15 tables let postgreSQL produces wrong
data
Details:

We have an situation where we must join ~30 tables to get a general table.
Don't ask why we do this this way.

After an unknown number of columns the joind values are not correct. We get
only the value from column 1.
If I separete the query and generate an temporary table with the first 20
tables and join them later with the rest one, all works fine.
All values in the result table are correct.

If you need more information, contact me I can send some example data.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2008-03-31 12:57:31 Re: BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data
Previous Message Tom Lane 2008-03-31 06:38:51 Re: Recommended approach for upgrading DBs with nonmatching encodings

Browse pgsql-patches by date

  From Date Subject
Next Message Pavel Stehule 2008-03-31 12:48:28 WIP: CASE statement for PL/pgSQL
Previous Message Zoltan Boszormenyi 2008-03-31 11:08:36 float4/float8/int64 passed by value with tsearch fixup