Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by hub.org (8.10.1/8.10.1) with ESMTP id e8TMnYp96819 for ; Fri, 29 Sep 2000 18:49:34 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.0/8.11.0) with ESMTP id e8TMnWB04539; Fri, 29 Sep 2000 18:49:32 -0400 (EDT) To: Jan Mlotkiewicz cc: pgsql-interfaces@postgresql.org Subject: Re: pg_aclcheck error? In-reply-to: <25497983.970265990598.JavaMail.imail@knuckles.excite.com> References: <25497983.970265990598.JavaMail.imail@knuckles.excite.com> Comments: In-reply-to Jan Mlotkiewicz message dated "Fri, 29 Sep 2000 15:19:50 -0700" Date: Fri, 29 Sep 2000 18:49:31 -0400 Message-ID: <4536.970267771@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200009/120 Jan Mlotkiewicz writes: > ERROR: pg_aclcheck: class "problem_seq_incident" not found. ^^^^^^^^^^^^^^^^^^^^ > My sequence is setup in the db config as problem_incident_seq, ^^^^^^^^^^^^^^^^^^^^ Is that just a typo in your message, or does it suggest that you didn't spell the sequence name the same everywhere? It looks like the sequence functions (nextval() etc) start out with a permissions check, so if you call them on a nonexistent sequence name the above complaint is what you'd get. regards, tom lane