From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New compile warnings for inheritance |
Date: | 2004-12-01 22:48:28 |
Message-ID: | 20324.1101941308@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> Tom Lane wrote:
>> Hmph. I'm unsure why there's a platform dependency there, but we should
>> probably just add an ORDER BY to suppress it. Will do.
> Why did it just appear? Optimizer changes in the past few days?
I did just change the planner, but what I don't understand at the moment
is why the results changed for me and not for you.
It looks like it's not actually the join to pg_class that is determining
this, but the plan used for the UPDATE just above it. That involves
only freshly-created tables and so it ought to be pretty much the same
planner problem for everyone. Odd. I'm building now on a Linux machine
to see if I can reproduce your result when using little-endian hardware.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2004-12-01 23:03:54 | Re: Fix for "q" with psql display paging dumps out of psql |
Previous Message | Tom Lane | 2004-12-01 22:43:35 | Re: libpq and psql not on same page about SIGPIPE |