| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Gregory Stark <stark(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Hans-Jürgen Schönig <postgres(at)cybertec(dot)at> |
| Subject: | Re: Mini improvement: statement_cost_limit |
| Date: | 2008-08-15 23:05:54 |
| Message-ID: | 200808151605.56557.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce,
> How about a simpler approach that throws an error or warning for
> cartesian products? That seems fool-proof.
Well, throwing a warning is pretty useless for an unattended application.
Also, it's perfectly possible to write queries which will never complete
without a cartesian join.
Basically, *unless* someone has a plan to integrate the greenplum resource
management stuff sometime soon, I think we should take Hans' idea (pending
patch quality, of course). There's an argument to be made that even if we
took the greenplum resource controller, statement_cost_limit would be much
simpler and worth having for the small-effort simple-application users.
FYI, the concept behind the Greenplum RM is similar, except that it
maintains a total "pool" of query costs on a per-role basis.
--
--Josh
Josh Berkus
PostgreSQL
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-08-16 00:17:07 | Re: psql bug -- using old variables and database connection |
| Previous Message | David E. Wheeler | 2008-08-15 22:44:16 | Re: Misusing functions taking "internal" via coincidental signature match |