From: Tom Lane <tgl@sss.pgh.pa.us>
To: William Wagman <szwagman@ad3.ucdavis.edu>
cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: Question re privileges on extensions
In-reply-to: 
 <32d712b7ef4d4606bd01d1ff17c0d090@BL2PR08MB113.namprd08.prod.outlook.com>
References: 
 <32d712b7ef4d4606bd01d1ff17c0d090@BL2PR08MB113.namprd08.prod.outlook.com>
Comments: In-reply-to William Wagman <szwagman@ad3.ucdavis.edu>
 message dated "Tue, 10 Jun 2014 23:22:59 -0000"
Date: Wed, 11 Jun 2014 14:27:17 -0400
Message-ID: <24587.1402511237@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

William Wagman <szwagman@ad3.ucdavis.edu> writes:
> The OEM plug-in sees everything but the sql information and the console
> displays a message indicating "pg_stat_statements status unknown, ensure
> data collection has occurred." I suspect that privileges on the
> pg_stat_statements extension is the issue.

There aren't really privileges associated with extensions.  My first
guess is that you created the extension in a different database than
the one the plug-in client is connecting to.

If you're not clear on what exactly the plug-in is doing, you could
try cranking log_statement up to "all" so that you can see its activity in
the postmaster log.  That might help diagnose what's going wrong.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin