Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1NL7Yx05241 for ; Fri, 23 Feb 2001 16:07:34 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f1NL7N900482; Fri, 23 Feb 2001 16:07:23 -0500 (EST) To: Dave Page cc: jhatfield@g-s.com.au, "'PostgreSQL Admin News'" Subject: Re: select * from pgadmin_users; causes error In-reply-to: <8568FC767B4AD311AC33006097BCD3D61A29C8@woody.vale-housing.co.uk> References: <8568FC767B4AD311AC33006097BCD3D61A29C8@woody.vale-housing.co.uk> Comments: In-reply-to Dave Page message dated "Fri, 23 Feb 2001 21:00:07 +0000" Date: Fri, 23 Feb 2001 16:07:23 -0500 Message-ID: <477.982962443@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200102/189 X-Sequence-Number: 792 Dave Page writes: > Basically it isn't so much as the user ID that created > the views that is an issue, it's that fact that pgAdmin then didn't issue a > 'GRANT ALL ON pgadmin_users TO PUBLIC'. The particular case being complained of here would not be fixed by that. regards, tom lane