Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: analyze anomalie


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Uwe Bartels <uwe(dot)bartels(at)gmail(dot)com>
  • Cc: pgsql-admin(at)postgresql(dot)org
  • Subject: Re: analyze anomalie
  • Date: Mon, 29 Jun 2009 10:29:34 -0400
  • Message-id: <11825.1246285774@sss.pgh.pa.us> <text/plain>

Uwe Bartels <uwe(dot)bartels(at)gmail(dot)com> writes:
> today i found an anomalie running
> analyze verbose <table>

> the output was simply "ANALYZE", which tells me that analyze was running
> successfully. but there was no verbose output. and in the statistics table
> was no updated last_analyze column.

Perhaps you didn't have permission to analyze the table, and had
client_min_messages set too high to see the resulting WARNING?
It would have done something like this:

regression=> analyze verbose tenk1;
WARNING:  skipping "tenk1" --- only table or database owner can analyze it
ANALYZE

but if the WARNING got suppressed it would match what you stated.

			regards, tom lane



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group