| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | ertan(dot)kucukoglu(at)1nar(dot)com(dot)tr, david(dot)g(dot)johnston(at)gmail(dot)com |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_dump problem with postgres user |
| Date: | 2023-02-12 21:15:05 |
| Message-ID: | 5dbb0065-e0ac-a74b-889f-d8b0669f36b0@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 2/12/23 13:10, ertan(dot)kucukoglu(at)1nar(dot)com(dot)tr wrote:
> Hello,
>
> My service provider spam filter just blocked your message and so I send a
> separate one.
>
> Your suspicion seems like correct. Postgres user is no more a superuser.
> Seems like they added postgresql_user and made it superuser.
Who is they?
> Is it possible to put everything back to normal?
If it was some outside entity that you don't know that changed the
permissions then you can't trust the instance any more.
> Can I use single user mode to change passwords and permissions?
>
> Thanks & Regards,
> Ertan
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zheng Li | 2023-02-13 04:20:29 | Re: Support logical replication of DDLs |
| Previous Message | ertan.kucukoglu | 2023-02-12 21:10:38 | Re: pg_dump problem with postgres user |