Re: [GENERAL] EXPLAIN SELECT .. does not return

2006-05-09 Thread David Link
Tom Lane wrote: David Link <[EMAIL PROTECTED]> writes: The following large EXPLAIN SELECT Statement fails to return, but continues to take up processing time until it is killed. [ 52-way join... ] Am I right in guessing that all the sales_xxx tables are the same size and have similar

Re: [GENERAL] EXPLAIN SELECT .. does not return

2006-03-29 Thread Tom Lane
David Link <[EMAIL PROTECTED]> writes: > The following large EXPLAIN SELECT Statement fails to return, but > continues to take up processing time until it is killed. > [ 52-way join... ] Am I right in guessing that all the sales_xxx tables are the same size and have similar statistics? I think t

[GENERAL] EXPLAIN SELECT .. does not return

2006-03-29 Thread David Link
Hi, The following large EXPLAIN SELECT Statement fails to return, but continues to take up processing time until it is killed. I've straightened up the postgresql.conf, as per Tom Lane's suggestions since last time I wrote about this. See: http://archives.postgresql.org/pgsql-general/2005-12

Re: [GENERAL] EXPLAIN SELECT .. does not return

2005-12-05 Thread Tom Lane
David Link <[EMAIL PROTECTED]> writes: > more importantly, do you think the problem I am having is due to these > configuration short comings? Yeah, the planning thresholds ... regards, tom lane ---(end of broadcast)--- TIP

Re: [GENERAL] EXPLAIN SELECT .. does not return

2005-12-05 Thread Joshua D. Drake
Thanks for your reply, Tom. Different folks have made different suggestions. Can you suggest more reasonable values for these? But more importantly, do you think the problem I am having is due to these configuration short comings? Thanks much. David take a look at: http://www.varlena.

Re: [GENERAL] EXPLAIN SELECT .. does not return

2005-12-05 Thread David Link
Tom Lane wrote: David Link <[EMAIL PROTECTED]> writes: Certain SQL Queries, I believe those with many table joins, when run as EXPLAIN plans, never return. I'd guess that one or all of these settings are excessive: geqo_threshold = 14 from_collapse_limit = 13 join_collapse_limit

Re: [GENERAL] EXPLAIN SELECT .. does not return

2005-12-05 Thread David Link
Jaime Casanova wrote: when you have thoses cases, you can take a look in pg_stats_activity to find the offending query... or simply logs all queries Thanks for the advice. I also turned on stat_command_string ---(end of broadcast)--- TIP 3:

Re: [GENERAL] EXPLAIN SELECT .. does not return

2005-12-05 Thread Tom Lane
David Link <[EMAIL PROTECTED]> writes: > Certain SQL Queries, I believe those with many table joins, when run as > EXPLAIN plans, never return. I'd guess that one or all of these settings are excessive: > geqo_threshold = 14 > from_collapse_limit = 13 > join_collapse_limit = 13 Keep in mind t

Re: [GENERAL] EXPLAIN SELECT .. does not return

2005-12-05 Thread Jaime Casanova
On 12/5/05, David Link <[EMAIL PROTECTED]> wrote: > Hi, This has become a major problem for us. Thank you in advance for > your help. > > OS: SUSE Linux 2.6.5-7.191-bigsmp > PostgreSQL: 7.4.8 > Application: ModPerl Web application using DBI.pm > Database size: 100 Gb, 1025 Tables. > > Problem: EXP

[GENERAL] EXPLAIN SELECT .. does not return

2005-12-05 Thread David Link
Hi, This has become a major problem for us. Thank you in advance for your help. OS: SUSE Linux 2.6.5-7.191-bigsmp PostgreSQL: 7.4.8 Application: ModPerl Web application using DBI.pm Database size: 100 Gb, 1025 Tables. Problem: EXPLAIN SELECT ... does not return. Description: The Application