From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dumpall -r -c try to drop user postgres |
Date: | 2017-12-12 05:23:43 |
Message-ID: | CAMkU=1zuWOTHDZVFbmfoj2ywtOVLU7FUUz_iLzzAZ6zbknQjog@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Dec 5, 2017 at 9:03 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
wrote:
> On Sun, Dec 3, 2017 at 3:21 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
>> wrote:
>> > I am not sure if user postgres should be removed, so it is probably bug
>> >
>> > pg_dumpall -r -c | grep postgres
>> >
>> > DROP ROLE postgres;
>> > CREATE ROLE postgres;
>>
>>
> I am not sure, if issue is in this code. But I am sure, so DROP ROLE
> postgres is just nonsense
>
> This command should to fail every time, and then should not be generated.
>
I don't see why it should fail every time.
Not all databases clusters were created with their initdb superuser being
'postgres'.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2017-12-12 05:29:43 | pgbench's expression parsing & negative numbers |
Previous Message | Jeff Janes | 2017-12-12 05:09:37 | Re: [HACKERS] postgres_fdw super user checks |