From: | Samuel Gendler <sgendler(at)ideasculptor(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Kris Jurka <books(at)ejurka(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: No hash join across partitioned tables? |
Date: | 2010-10-18 06:13:01 |
Message-ID: | AANLkTim3PgeBNsGujstuAD-Z+TPNgQ+7Ucw3Oy87hAAb@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-performance |
On Sat, Oct 16, 2010 at 8:29 AM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com>wrote:
> Excerpts from Samuel Gendler's message of sáb oct 16 02:35:46 -0300 2010:
>
> > An issue with automatically analyzing the entire hierarchy is 'abstract'
> > table definitions. I've got a set of tables for storing the same data at
> > different granularities of aggregation. Within each granularity, I've
> got
> > partitions, but because the set of columns is identical for each
> > granularity, I've got an abstract table definition that is inherited by
> > everything. I don't need or want statistics kept on that table because I
> > never query across the abstract table, only the parent table of each
> > aggregation granularity
>
> Hmm, I think you'd be better served by using LIKE instead of regular
> inheritance.
>
>
Yep. I inherited the architecture, though, and changing it hasn't been a
high priority.
--sam
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2010-10-18 07:03:50 | Re: Timeout and wait-forever in sync rep |
Previous Message | Jeff Davis | 2010-10-18 05:53:45 | Serializable snapshot isolation patch |
From | Date | Subject | |
---|---|---|---|
Next Message | Vitalii Tymchyshyn | 2010-10-18 07:58:39 | Re: Select count(*), the sequel |
Previous Message | AI Rumman | 2010-10-18 05:16:11 | how to get the total number of records in report |