From: | Samuel Gendler <sgendler(at)ideasculptor(dot)com> |
---|---|
To: | Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: oracle to psql migration - slow query in postgres |
Date: | 2010-10-15 08:12:54 |
Message-ID: | AANLkTikjAhheQmVu1ZE6a8e53amvC091+B-PkDePJ_63@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
On Thu, Oct 14, 2010 at 8:59 PM, Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com>wrote:
> If working with partitioning, be very aware that PostgreSQL optimizer has
> certain problems with partitions, especially with group functions. If you
> want speed, everything must be prefixed with partitioning column: indexes,
> expressions, joins. There is no explicit star schema and creating hash
> indexes will not buy you much, as a matter of fact, Postgres community is
> extremely suspicious of the hash indexes and I don't see them widely used.
> Having said that, I was able to solve the problems with my speed and
> partitioning.
>
>
Could you elaborate on this, please? What do you mean by 'everythin must be
prefixed with partitioning column?'
--sam
From | Date | Subject | |
---|---|---|---|
Next Message | Mladen Gogala | 2010-10-15 14:51:48 | Re: oracle to psql migration - slow query in postgres |
Previous Message | Guillaume Lelarge | 2010-10-15 06:27:08 | Re: How to find the primary server of a hot standby server? |
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim GÜNDÜZ | 2010-10-15 08:36:26 | Re: Slow count(*) again... |
Previous Message | Jesper Krogh | 2010-10-15 05:04:43 | Re: Slow count(*) again... |