Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> The optimizer seems to want to use sequential scans on inherited tables
> when crossed with another table, as the following seems to demonstrate:

Is it intentional that your test case omits an analyze on t2?  Coz when
I add that, I get the same plan you show for 8.0.  Without the knowledge
that t2 is small, that plan is not a good choice.

(The larger point that joins of inheritance unions aren't well-planned
is true, but it's always been true...)

			regards, tom lane

In response to

• Optimizer oddness, possibly compounded in 8.1 at 2005-12-02 14:55:09 from Philip Warner

Responses

• Re: Optimizer oddness, possibly compounded in 8.1 at 2005-12-03 00:35:04 from Philip Warner

pgsql-hackers by date

Next:	From: Bruce Momjian	Date: 2005-12-02 16:47:22
	Subject: Re: Numeric 508 datatype
Previous:	From: Jaime Casanova	Date: 2005-12-02 15:30:10
	Subject: Re: Graphics in postgress using GTK