Re: [HACKERS] statement_cost_limit for regression testing.

2008-09-02 Thread Pavel Stehule
2008/9/2 Ryan Bradetich <[EMAIL PROTECTED]>: > Hello Simon, > > On Mon, Sep 1, 2008 at 9:35 AM, Simon Riggs <[EMAIL PROTECTED]> wrote: >> On Thu, 2008-08-28 at 19:57 -0700, Ryan Bradetich wrote: >>> I just wanted to throw out another possible use for this GUC. There >>> maybe a better way to >>>

Re: [HACKERS] statement_cost_limit for regression testing.

2008-09-02 Thread Ryan Bradetich
Hello Simon, On Mon, Sep 1, 2008 at 9:35 AM, Simon Riggs <[EMAIL PROTECTED]> wrote: > On Thu, 2008-08-28 at 19:57 -0700, Ryan Bradetich wrote: >> I just wanted to throw out another possible use for this GUC. There >> maybe a better way to >> solve this problem, but I believe this patch would be

Re: [HACKERS] statement_cost_limit for regression testing.

2008-09-02 Thread Simon Riggs
On Thu, 2008-08-28 at 19:57 -0700, Ryan Bradetich wrote: > I am not sure of the status of the patch, but I did read through the > thread at: >http://archives.postgresql.org/pgsql-hackers/2008-08/msg00054.php > > > I just wanted to throw out another possible use for this GUC. There > maybe

[HACKERS] statement_cost_limit for regression testing.

2008-08-28 Thread Ryan Bradetich
Hello, Sorry for the new thread on this topic, I did not have a copy in my inbox I could replay to :( I am not sure of the status of the patch, but I did read through the thread at: http://archives.postgresql.org/pgsql-hackers/2008-08/msg00054.php I just wanted to throw out another possible

Re: [HACKERS] statement_cost_limit

2006-03-01 Thread Bruce Momjian
I can see this as useful for newbies who don't want to accidentally overload the system. --- Simon Riggs wrote: > On Wed, 2006-03-01 at 11:47 -0500, Tom Lane wrote: > > Simon Riggs <[EMAIL PROTECTED]> writes: > > > A new par

Re: [HACKERS] statement_cost_limit

2006-03-01 Thread Simon Riggs
On Wed, 2006-03-01 at 11:47 -0500, Tom Lane wrote: > Simon Riggs <[EMAIL PROTECTED]> 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

Re: [HACKERS] statement_cost_limit

2006-03-01 Thread Tom Lane
Simon Riggs <[EMAIL PROTECTED]> 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

[HACKERS] statement_cost_limit

2006-03-01 Thread Simon Riggs
On Tue, 2006-02-21 at 11:45 +1300, Mark Kirkwood wrote: > Simon Riggs wrote: > > A new parameter that allows the administrator to place sensible limits > > on the size of queries executed. > > > > This is useful for ad-hoc SQL access > > - when a very large table cannot realistically be sorted e