| From: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> |
|---|---|
| To: | Mahendra Singh Thalor <mahi6run(at)gmail(dot)com> |
| Cc: | Vaibhav Dalvi <vaibhav(dot)dalvi(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Non-text mode for pg_dumpall |
| Date: | 2025-12-12 13:40:02 |
| Message-ID: | CAC6VRoY6Vpm01hOnp2F=gyNt_f6rCz9kuESmgP524mQnruEVJQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Dec 11, 2025 at 9:39 PM Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>
wrote:
>
>
> Here, in our case, as the cluster already has a role with the current
> user in restore, we are reporting error "pg_restore: error: could not
> execute query: ERROR: role "role" already exists" and after this
> error, restore is exiting.
>
> If you restore using a different role, then you will not get any error
> and the full cluster will be restored. I will add some handling to
> ignore the "CREATE ROLE current_user" command in pg_restore.
>
> Thanks Mahendra, Could you please also add some error message for this
below
pg_restore command:
postgres=# create table t(n int);
CREATE TABLE
postgres=# insert into t values (1),(10),(100);
INSERT 0 3
Perform pg_dump: ./pg_dump -Ft -f a.a1 postgres
Perform pg_restore: /pg_restore -Ft a.a1 -f -C -v
pg_restore: creating TABLE "public.t"
pg_restore: processing data for table "public.t"
[edb(at)1a1c15437e7c bin]$ ./psql postgres
psql (19devel)
Type "help" for help.
postgres=# \dt
Did not find any tables.
postgres=#
regards,
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2025-12-12 13:45:46 | Re: Import Statistics in postgres_fdw before resorting to sampling. |
| Previous Message | Álvaro Herrera | 2025-12-12 13:33:50 | Re: weird ON CONFLICT clauses |