Re: statement_cost_limit - Mailing list pgsql-hackers

From Tom Lane
Subject Re: statement_cost_limit
Date
Msg-id 11540.1141231669@sss.pgh.pa.us
Whole thread Raw
In response to statement_cost_limit  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: statement_cost_limit  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.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


pgsql-hackers by date:

Previous
From: Lamar Owen
Date:
Subject: Re: pg_config, pg_service.conf, postgresql.conf ....
Next
From: Bruce Momjian
Date:
Subject: Re: Automatic free space map filling