pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rod Taylor <pg@rbt.ca>
Cc: Greg Stark <gsstark@mit.edu>
Cc: pgsql-hackers@postgresql.org, Gurmeet Manku <manku@cs.stanford.edu>
Subject: Re: [PERFORM] Bad n_distinct estimation; hacks suggested?
Date: Wed, 27 Apr 2005 00:14:36 -0400
Message-ID: <17677.1114575276@sss.pgh.pa.us> (raw)
In-Reply-To: <1114560992.77587.112.camel@home>
References: <Pine.LNX.4.44.0504261443340.12051-100000@xenon.Stanford.EDU>
	<87u0lt5efo.fsf@stark.xeocode.com>
	<1114557011.77587.107.camel@home>
	<87oec15d9m.fsf@stark.xeocode.com>
	<1114560992.77587.112.camel@home>

Rod Taylor <pg@rbt.ca> writes:
> If when we have partitions, that'll be good enough. If partitions aren't
> available this would be quite painful to anyone with large tables --
> much as the days of old used to be painful for ANALYZE.

Yeah ... I am very un-enthused about these suggestions to make ANALYZE
go back to doing a full scan ...

			regards, tom lane



view thread (53+ messages)  latest in thread

Message-ID: <17677.1114575276@sss.pgh.pa.us>
Permalink:  ../17677.1114575276@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/17677.1114575276@sss.pgh.pa.us

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pg@rbt.ca, gsstark@mit.edu, manku@cs.stanford.edu
  Subject: Re: [PERFORM] Bad n_distinct estimation; hacks suggested?
  In-Reply-To: <17677.1114575276@sss.pgh.pa.us>

* 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