Re: Optimizer oddness, possibly compounded in 8.1

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Hannu Krosing <hannu(at)skype(dot)net>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Philip Warner <pjw(at)rhyme(dot)com(dot)au>, pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Optimizer oddness, possibly compounded in 8.1
Date: 2005-12-06 18:32:53
Message-ID: 1133893973.2906.876.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 2005-12-06 at 16:12 +0200, Hannu Krosing wrote:
> Ühel kenal päeval, L, 2005-12-03 kell 09:21, kirjutas Simon Riggs:
>
> > First off, I think we need to do some more work on partitioning so that
> > some knowledge about the union set is understood by the optimizer. At
> > the moment there is no concept of partition key, so its hard to spot
> > when two union sets have the same key to allow pushdown.
>
> One of the easier cases would be non-overlapping (exclusive) constraints
> on union subtables on the joined column.
>
> This could serve as a "partition key", or in case of many nonoverlapping
> columns (ex.: table is partitioned by date and region), as many
> partition keys.

Yes, thats my planned direction.

Best Regards, Simon Riggs

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-12-06 19:26:38 Re: Upcoming PG re-releases
Previous Message Bruce Momjian 2005-12-06 18:27:49 Re: Reduce NUMERIC size by 2 bytes, reduce max length to 508