Thanks very much for your response and for writing the bug report. Lynn On 10/31/17, 7:15 AM, "users-list on behalf of Panagiotis Koutsourakis" <users-list-bounces+lcj34=cornell.edu@monetdb.org on behalf of kutsurak@monetdbsolutions.com> wrote: Hi Lynn, This is not a problem with your db. Any user should be able to select from the tables sys.object, sys.keys and sys.idxs, so this is a bug. I have filed it at https://www.monetdb.org/bugzilla/show_bug.cgi?id=6457 where you can follow the progress. Best regards, Panos. Lynn Carol Johnson @ 2017-10-30 10:57 GMT: > Monetdb team – > > Any answer on this question? Do you expect non-admin users of monetdb to need access to sys.objects, sys.keys and sys.idxs in order to perform “select” statements on tables in user schema? > > Thanks - Lynn > > From: users-list <users-list-bounces+lcj34=cornell.edu@monetdb.org> on behalf of Lynn Carol Johnson <lcj34@cornell.edu> > Reply-To: Communication channel for MonetDB users <users-list@monetdb.org> > Date: Thursday, October 26, 2017 at 4:45 PM > To: Communication channel for MonetDB users <users-list@monetdb.org> > Subject: latest version question > > Hello monetdb team – > > We upgraded this afternoon to the latest version of monetdb (Jul2017-SP2). When testing access for my lab, I noticed the general login could no longer perform the command: > > \d <table_name> > > The errors were related to missing group access to sys.objects, sys.keys and sys.idxs. When, as monetdb admin, I granted “select” on these tables, the “\d <table_name>” command then worked. > > Is this something new, or does it indicate a problem with the db ? It was not necessary to grant general users permission to these system tables previously. > > Thanks - Lynn > _______________________________________________ > users-list mailing list > users-list@monetdb.org > https://www.monetdb.org/mailman/listinfo/users-list