Re: analyze anomalie
| От | Uwe Bartels |
|---|---|
| Тема | Re: analyze anomalie |
| Дата | |
| Msg-id | 8ea917510906290738pabe5613l1912345eb670dcbc@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: analyze anomalie (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | 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
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@sss.pgh.pa.us>
Uwe Bartels <uwe.bartels@gmail.com> writes:Perhaps you didn't have permission to analyze the table, and had
> 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.
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
В списке pgsql-admin по дате отправления: