pg_dump permissions problem

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: pgsql-hackers(at)postgresql(dot)org
Subject: pg_dump permissions problem
Date: 2003-09-29 09:44:35
Message-ID: 3F77FF03.8060903@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi guys,

My live 7.3.4 database dumps data like this:

SET SESSION AUTHORIZATION 'auadmin';

--
-- TOC entry 346 (OID 1012952)
-- Name: log_freeprofile; Type: TABLE; Schema: public; Owner: auadmin
--

CREATE TABLE log_freeprofile (
date date DEFAULT ('now'::text)::date NOT NULL,
"start" integer DEFAULT '0',
complete integer DEFAULT '0',
gotojoin integer DEFAULT '0',
payment integer DEFAULT '0',
done integer DEFAULT '0',
joined integer DEFAULT '0'
);

--
-- TOC entry 347 (OID 1012952)
-- Name: log_freeprofile; Type: ACL; Schema: public; Owner: auadmin
--

REVOKE ALL ON TABLE log_freeprofile FROM PUBLIC;
GRANT ALL ON TABLE log_freeprofile TO brett;
GRANT INSERT,SELECT,UPDATE ON TABLE log_freeprofile TO "au-php";
GRANT SELECT ON TABLE log_freeprofile TO GROUP readonly;
REVOKE ALL ON TABLE log_freeprofile FROM auadmin;

Now, loading this into 7.4beta3 gives this error:

ERROR: dependent privileges exist

When executing the REVOKE ALL line.

I think this occurs because we do all the grants as auadmin, not as the
superuser loading the file. This means that all the grants that we
grant are dependent privilegs, and hence that REVOKE line needs a
CASCADE option.

Actually, why does that line even exist!?!? Why do we need to REVOKE
ALL from the table owner??

What should we do about this?

Chris

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2003-09-29 09:57:13 Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta)
Previous Message strk 2003-09-29 09:34:34 finding memory leaks in extensions