-Ursprüngliche Nachricht-
Von: Tom Lane [mailto:[EMAIL PROTECTED]
Gesendet: Donnerstag, 3. April 2008 21:33
An: Heikki Linnakangas
Cc: Alvaro Herrera; pgsql-patches; Ceschia, Marcello; PostgreSQL Bugs
Betreff: Re: [PATCHES] Re: [BUGS] BUG #4070: Join more then ~15 tables let
postgreSQL
Heikki Linnakangas [EMAIL PROTECTED] writes:
On second thought, expanding AttrNumber to int32, wholesale, might not
be a good idea,
No, it wouldn't. For one thing it'd be a protocol break --- column
numbers are int16 --- and for another, we'd have terrible performance
problems with such wide
Tom Lane wrote:
Heikki Linnakangas [EMAIL PROTECTED] writes:
On second thought, expanding AttrNumber to int32, wholesale, might not
be a good idea,
No, it wouldn't. For one thing it'd be a protocol break --- column
numbers are int16 ---
I wasn't planning to change that.
and for another,
Heikki Linnakangas [EMAIL PROTECTED] writes:
Tom Lane wrote:
Actually rows are supposed to be limited
to ~1600 columns, anyway, because of HeapTupleHeader limitations.
The trick is that that limitation doesn't apply to the intermediate
virtual tuples we move around in the executor.
I'm
Tom Lane wrote:
I still haven't seen the actual bug description come by here, and the
pgsql-bugs archive hasn't got it either.
http://archives.postgresql.org/pgsql-bugs/2008-03/msg00351.php
and continues in April here
http://archives.postgresql.org/pgsql-bugs/2008-04/msg00031.php
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
I still haven't seen the actual bug description come by here, and the
pgsql-bugs archive hasn't got it either.
(apparently some mails on that thread are missing ...)
That's what I meant. Heikki is quoting himself from a message that
Tom Lane wrote:
That's what I meant. Heikki is quoting himself from a message that
hasn't appeared anywhere public, and he must have had at least one
message from the OP that hasn't appeared either. So the rest of us
are still mostly in the dark about the problem.
I got this one, which
Tom Lane wrote:
Alvaro Herrera [EMAIL PROTECTED] writes:
Tom Lane wrote:
I still haven't seen the actual bug description come by here, and the
pgsql-bugs archive hasn't got it either.
(apparently some mails on that thread are missing ...)
That's what I meant. Heikki is quoting himself
Heikki Linnakangas [EMAIL PROTECTED] writes:
Oh, the query actually gives an assertion failure on an
assertion-enabled build, so this is clearly a bug:
TRAP: FailedAssertion(!(attnum 0 attnum =
list_length(rte-joinaliasvars)), File: parse_relation.c, Line: 1697)
Okay, I looked at this
