pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Palle Girgensohn <girgen@pingpong.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: select max(field) from table much faster with a group by clause?
Date: Thu, 01 Nov 2007 11:34:42 -0400
Message-ID: <6024.1193931282@sss.pgh.pa.us> (raw)
In-Reply-To: <16563C7D831BD7B32DFBDDEC@rambutan.pingpong.net>
References: <D26563C7B9CCEB0A338FF08E@rambutan.pingpong.net>
	<4305.1193924619@sss.pgh.pa.us>
	<DFCABF1E9EE0F7A9D44CA50A@rambutan.pingpong.net>
	<5504.1193929617@sss.pgh.pa.us>
	<16563C7D831BD7B32DFBDDEC@rambutan.pingpong.net>

Palle Girgensohn <girgen@pingpong.net> writes:
> --On torsdag, november 01, 2007 11.06.57 -0400 Tom Lane <tgl@sss.pgh.pa.us> 
> wrote:
>> Um, you did re-ANALYZE the table after changing the setting?

> alter table login alter userid SET statistics 1000;
> vacuum analyze login;

Hm, that's the approved procedure all right.  But the plans didn't
change at all?  Not even the estimated number of rows?

			regards, tom lane



view thread (11+ messages)  latest in thread

Message-ID: <6024.1193931282@sss.pgh.pa.us>
Permalink:  ../6024.1193931282@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/6024.1193931282@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, girgen@pingpong.net
  Subject: Re: select max(field) from table much faster with a group by clause?
  In-Reply-To: <6024.1193931282@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