pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Trevor Talbot <quension@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: TB-sized databases
Date: Fri, 30 Nov 2007 02:15:45 -0800
Message-ID: <90bce5730711300215x3ff6c68ekf1c55ce799e48578@mail.gmail.com> (raw)
In-Reply-To: <878x4hmfd4.fsf@oxford.xeocode.com>
References: <4544e0330711260904g45d893a8ub1731e245aa8fc84@mail.gmail.com>
	<474B1B8C.1030505@gmail.com>
	<4544e0330711271218h56ce4cc3p280a9fefff24583d@mail.gmail.com>
	<1196197045.4246.1154.camel@ebony.site>
	<474CA2FA.2020201@laotraesquina.com.ar>
	<Pine.LNX.4.58.0711281248290.3731@aragorn.flymine.org>
	<20071128082716.91bbad9c.wmoran@collaborativefusion.com>
	<1196257702.31315.6.camel@PCD12478>
	<1196270576.4246.1246.camel@ebony.site>
	<878x4hmfd4.fsf@oxford.xeocode.com>

On 11/29/07, Gregory Stark <stark@enterprisedb.com> wrote:
> "Simon Riggs" <simon@2ndquadrant.com> writes:
> > On Wed, 2007-11-28 at 14:48 +0100, Csaba Nagy wrote:

> >> In fact an even more useful option would be to ask the planner to throw
> >> error if the expected cost exceeds a certain threshold...

> > Tom's previous concerns were along the lines of "How would know what to
> > set it to?", given that the planner costs are mostly arbitrary numbers.

> Hm, that's only kind of true.

> Obviously few people know how long such a page read takes but surely you would
> just run a few sequential reads of large tables and set the limit to some
> multiple of whatever you find.
>
> This isn't going to precise to the level of being able to avoid executing any
> query which will take over 1000ms. But it is going to be able to catch
> unconstrained cross joins or large sequential scans or such.

Isn't that what statement_timeout is for? Since this is entirely based
on estimates, using arbitrary fuzzy numbers for this seems fine to me;
precision isn't really the goal.



view thread (61+ messages)  latest in thread

Message-ID: <90bce5730711300215x3ff6c68ekf1c55ce799e48578@mail.gmail.com>
Permalink:  ../90bce5730711300215x3ff6c68ekf1c55ce799e48578@mail.gmail.com/
Also on:    postgresql.org/message-id/90bce5730711300215x3ff6c68ekf1c55ce799e48578@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: quension@gmail.com
  Subject: Re: TB-sized databases
  In-Reply-To: <90bce5730711300215x3ff6c68ekf1c55ce799e48578@mail.gmail.com>
  References: <4544e0330711260904g45d893a8ub1731e245aa8fc84@mail.gmail.com> <474B1B8C.1030505@gmail.com> <4544e0330711271218h56ce4cc3p280a9fefff24583d@mail.gmail.com> <1196197045.4246.1154.camel@ebony.site> <474CA2FA.2020201@laotraesquina.com.ar> <Pine.LNX.4.58.0711281248290.3731@aragorn.flymine.org> <20071128082716.91bbad9c.wmoran@collaborativefusion.com> <1196257702.31315.6.camel@PCD12478> <1196270576.4246.1246.camel@ebony.site> <878x4hmfd4.fsf@oxford.xeocode.com> <90bce5730711300215x3ff6c68ekf1c55ce799e48578@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox