Re: How to restore database without re-write database and tables owner by using postgres

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Cidy Long <cidy(dot)long(at)gmail(dot)com>
Cc: "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: How to restore database without re-write database and tables owner by using postgres
Date: 2023-05-22 13:42:52
Message-ID: CAKFQuwZ9UojAhSEnjUsKPDDj6MfMxZkDtFerOK5j=xLYSKLGjg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Saturday, May 20, 2023, Cidy Long <cidy(dot)long(at)gmail(dot)com> wrote:

> Hi. Here.
>
> I’m trying to restore multiple database backup tar files to new database
> server on PostgreSQL-15 by run command in shell script
>
> /usr/pgsql-15/bin/pg_restore -v --no-owner --host=$h --port=$db_port
> --username=postgres --dbname=$db_name $db_tar_file
>
> but I found, the restored database’s owner and its tables owner was
> replaced by connect user (super user——postgres).
>
> I tired to find out How to keep the database and its table original owner,
> I don’t find any thing.
>
> Please advise
>

This isn’t a bug, requests for help should be directed to the -general list.
Using colors makes your e-mail hard to read on a white background.
‘you told it “no owner” which does exactly what you’ve described here.

David J.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tristan Partin 2023-05-22 17:04:58 Re: BUG #17698: On SIGTERM, psql terminates, but leaves the statement running
Previous Message Tom Lane 2023-05-22 13:40:28 Re: Clause accidentally pushed down ( Possible bug in Making Vars outer-join aware)