Re: analyze anomalie

From: Uwe Bartels <uwe(dot)bartels(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: analyze anomalie
Date: 2009-06-29 14:38:46
Message-ID: 8ea917510906290738pabe5613l1912345eb670dcbc@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi Tom,

I was running the command as user postgres (default). The "vacuum anlyze"
and the "analyze" I run as the same user.
client_min_messages is still set to default in the server config.

reagrds,
Uwe

2009/6/29 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>

> 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
>

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Kevin Grittner 2009-06-29 15:11:39 Re: unable to create new table
Previous Message Tom Lane 2009-06-29 14:29:34 Re: analyze anomalie