| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Joao Miguel Ferreira <joao(dot)miguel(dot)c(dot)ferreira(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: permission denied to create and drop user |
| Date: | 2021-02-02 22:54:51 |
| Message-ID: | eadf39ed-6252-b685-6016-3c931e7dbf1b@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/2/21 2:43 PM, Joao Miguel Ferreira wrote:
> Hi,
>
>
> But... my dump file contains some agressive commands that are actually
> making a reall mess. here they are:
>
> CREATE ROLE pgcon;
> ALTER ROLE pgcon WITH NOSUPERUSER INHERIT NOCREATEROLE NOCREATEDB LOGIN
> NOREPLICATION NOBYPASSRLS;
> CREATE ROLE postgres;
> ALTER ROLE postgres WITH NOSUPERUSER INHERIT NOCREATEROLE NOCREATEDB
> LOGIN NOREPLICATION NOBYPASSRLS;
>
> that is why I messed up my database. Lucky it is not critical at all. I
> can start all over again, no problem.
>
> maybe "pg_dumpall" has options to avoid those changes?
>
That would be attributing AI abilities to pg_dumpall that it does not
have. Those commands got there from someone in the original database
tinkering with grants.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Cherio | 2021-02-03 06:43:14 | Re: count(*) vs count(id) |
| Previous Message | Joao Miguel Ferreira | 2021-02-02 22:43:13 | Re: permission denied to create and drop user |