X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id 141999DCAE2
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Thu, 15 Dec 2005 07:04:01 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 70441-01
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Thu, 15 Dec 2005 07:04:02 -0400 (AST)
Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159])
	by postgresql.org (Postfix) with ESMTP id 324669DCAB1
	for <pgsql-performance@postgresql.org>;
	Thu, 15 Dec 2005 07:03:58 -0400 (AST)
Received: from mail.logix-tt.com (serval.logix-tt.com [213.239.221.42])
	by svr4.postgresql.org (Postfix) with ESMTP id 2D7A25AF02E
	for <pgsql-performance@postgresql.org>;
	Thu, 15 Dec 2005 11:04:01 +0000 (GMT)
Received: from kingfisher.intern.logix-tt.com (Ka199.k.pppool.de
	[85.75.161.153])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mail.logix-tt.com (Postfix) with ESMTP id 86D5924400F;
	Thu, 15 Dec 2005 12:10:09 +0100 (CET)
Received: from [127.0.0.1] (localhost [127.0.0.1])
	by kingfisher.intern.logix-tt.com (Postfix) with ESMTP id E407F2DDA;
	Thu, 15 Dec 2005 12:03:23 +0100 (CET)
Message-ID: <43A14D7B.8030705@logix-tt.com>
Date: Thu, 15 Dec 2005 12:03:23 +0100
From: Markus Schaber <schabi@logix-tt.com>
Organization: Logical Tracking and Tracing International AG, Switzerland
User-Agent: Debian Thunderbird 1.0.7 (X11/20051017)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: PostGIS Users Discussion <postgis-users@postgis.refractions.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: [postgis-users] Is my query planner failing me, or vice versa?
References: 
 <71E37EF6B7DCC1499CEA0316A2568328024BBCD3@loki.wc.globexplorer.net>
In-Reply-To: 
 <71E37EF6B7DCC1499CEA0316A2568328024BBCD3@loki.wc.globexplorer.net>
X-Enigmail-Version: 0.93.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=0 required=5 tests=[none]
X-Spam-Score: 0
X-Spam-Level: 
X-Archive-Number: 200512/354
X-Sequence-Number: 16175

Hi, Gregory,

Gregory S. Williamson wrote:
> Forgive the cross-posting, but I found myself wondering if might not
> be some way future way of telling the planner that a given table
> (column ?) has a high likelyhood of being TOASTed. Similar to the
> random_page_cost in spirit. We've got a lot of indexed data that is
> spatial and have some table where no data is toasted (road segments)
> and others where evrything is.

I'd personally put this into ANALYZE, it already collects statistics, so
it could also calculate TOASTing likelyhood and average TOASTed size.

Maybe that 8.X PostgreSQL already does this, I'm a bit lagging :-)

Markus