Ow Mun Heng <[EMAIL PROTECTED]> writes:
> Queries involves 11 Joins (of 5 Main tables, of which 3 are Large, 2 are
> fact tables)
It would be a good idea to increase join_collapse_limit to more than 11.
This will increase the planning time, but the investment will likely be
worthwhile for such a l
On Fri, 2007-08-03 at 07:55 -0600, Josh Tolley wrote:
> On 8/3/07, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> > Can anyone shed some light on this. I just would like to know if
> queries
> > for raw data (not aggregregates) is expected to take a long time.
> > Running times between 30 - 2 hours for l
"Tom Lane" <[EMAIL PROTECTED]> writes:
> Ow Mun Heng <[EMAIL PROTECTED]> writes:
>> Can anyone shed some light on this. I just would like to know if queries
>> for raw data (not aggregregates) is expected to take a long time.
>> Running times between 30 - 2 hours for large dataset pulls.
>
>> Invo
On Fri, 2007-08-03 at 15:12 +0800, Ow Mun Heng wrote:
> Is 30min - 2hours too long or is this considered "normal"??
Yes.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---(end of broadcast)---
TIP 6: explain analyze is your friend
Ow Mun Heng escreveu:
Can anyone shed some light on this. I just would like to know if queries
for raw data (not aggregregates) is expected to take a long time.
Running times between 30 - 2 hours for large dataset pulls.
Involves lots of joins on very large tables (min 1 millon rows each
table,
Ow Mun Heng <[EMAIL PROTECTED]> writes:
> Can anyone shed some light on this. I just would like to know if queries
> for raw data (not aggregregates) is expected to take a long time.
> Running times between 30 - 2 hours for large dataset pulls.
> Involves lots of joins on very large tables (min 1
On 8/3/07, Ow Mun Heng <[EMAIL PROTECTED]> wrote:
> Can anyone shed some light on this. I just would like to know if queries
> for raw data (not aggregregates) is expected to take a long time.
> Running times between 30 - 2 hours for large dataset pulls.
>
> Involves lots of joins on very large tab
