RE: Re: WARNING: skipping "pg_database" --- only superuser can analyze it

From: "Abraham, Danny" <danny_abraham(at)bmc(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: RE: Re: WARNING: skipping "pg_database" --- only superuser can analyze it
Date: 2021-06-28 17:57:06
Message-ID: PH0PR02MB744648AB163C03D7A5142D4A8E039@PH0PR02MB7446.namprd02.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Right to the point ==> set client_min_messages=error; Solved it

Thanks

-----Original Message-----
From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Sent: Monday, June 28, 2021 5:53 PM
To: Abraham, Danny <danny_abraham(at)bmc(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: [EXTERNAL] Re: WARNING: skipping "pg_database" --- only superuser can analyze it

"Abraham, Danny" <danny_abraham(at)bmc(dot)com> writes:
> Good old "analyze;" will run smoothly on 11.5...
> But on 12.6 will skip and warn on any pg_catalog/information_schema table.

Hm, for me there are such warnings on 11.x too. Not as many --- it looks like indexes are mentioned as well in 12.x. But it's never been the case that this was entirely silent for an unprivileged user.

> Questions: 1. Has the behavior changed in 12.6? 2.How can I analyze on public tables (No syntax like analyze schema=public)

If you don't want to see the warnings, consider

set client_min_messages to error;

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Shubham Mittal 2021-06-28 18:28:58 Use case stuck due to Partitioning
Previous Message Joshua Drake 2021-06-28 16:28:45 Re: Ubuntu 14.04 (trusty) Postgres 13 deb package