Re: statement_cost_limit

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: statement_cost_limit
Date: 2006-03-01 16:47:49
Message-ID: 11540.1141231669@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> A new parameter that allows the administrator to place sensible limits
> on the size of queries executed.

As I said when the idea was floated originally, I don't think this is a
very good idea at all. The planner's estimates are sufficiently often
wrong that refusing to execute queries on the strength of an estimated
cost is going to burn you in both directions.

Even if it were a good idea, the proposed location of the test is 100%
wrong, as you are only guarding one path of query submission. Or were
you intending that the restriction be trivial to subvert?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-03-01 16:57:09 Re: Automatic free space map filling
Previous Message Lamar Owen 2006-03-01 16:42:05 Re: pg_config, pg_service.conf, postgresql.conf ....