RE: error restoring backup in version 4.4.1

Lists: pgadmin-support
From: "Gareth Vaughan" <gareth(at)specialisedstructures(dot)co(dot)nz>
To: <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: error restoring backup in version 4.4.1
Date: 2019-01-20 20:57:22
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Lists: pgadmin-support

Hi pgAdmin support

Thanks for the new version. I've tried updating but I've encountered a small error.

I'm currently running postgres 10.4. I generate backups with something like:

pg_dump.exe -Fc -U myRoleName -h localhost -p 5432 --dbname=myDb --file=dbBackup.backup

To restore a backup to a new db in pgAdmin

1) create a new db via the Create - Database dialogue accessible from the browser panel

2) right click on the newly created db and select restore

3) navigate to the backup file, select the rolename and click restore

in pgadmin 4.3.6

this process completes successfully

in pgadmin 4.4.1 this fails with

Failed (exit code 1)

here's the error from the detailed report:

pg_restore: creating SCHEMA "public"

pg_restore: [archiver (db)] Error while PROCESSING TOC:

pg_restore: [archiver (db)] Error from TOC entry 3; 2615 2200 SCHEMA public myRoleName

pg_restore: [archiver (db)] could not execute query: ERROR: schema "public" already exists

Command was: CREATE SCHEMA public;

Thanks, Gareth


From: Ricardo Martin Gomez <rimartingomez(at)hotmail(dot)com>
To: "pgadmin-support(at)lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>, Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz>
Subject: Re: error restoring backup in version 4.4.1
Date: 2019-01-21 00:58:56
Message-ID: SC1P15201MB2304D83D3362350871683478A39F0@SC1P15201MB2304.LAMP152.PROD.OUTLOOK.COM
Views: Whole Thread | Raw Message | Download mbox | Resend email
Lists: pgadmin-support

Hi Garreth,
When you run second restore.
Is the target database recreated recently?

Obtener Outlook para Android<https://aka.ms/ghei36>

________________________________
From: Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz>
Sent: Sunday, January 20, 2019 5:57:22 PM
To: pgadmin-support(at)lists(dot)postgresql(dot)org
Subject: error restoring backup in version 4.4.1

Hi pgAdmin support

Thanks for the new version. I've tried updating but I've encountered a small error.

I'm currently running postgres 10.4. I generate backups with something like:
pg_dump.exe -Fc -U myRoleName -h localhost -p 5432 --dbname=myDb --file=dbBackup.backup

To restore a backup to a new db in pgAdmin
1) create a new db via the Create - Database dialogue accessible from the browser panel
2) right click on the newly created db and select restore
3) navigate to the backup file, select the rolename and click restore

in pgadmin 4.3.6
this process completes successfully

in pgadmin 4.4.1 this fails with
Failed (exit code 1)
here's the error from the detailed report:

pg_restore: creating SCHEMA "public"
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 3; 2615 2200 SCHEMA public myRoleName
pg_restore: [archiver (db)] could not execute query: ERROR: schema "public" already exists
Command was: CREATE SCHEMA public;

Thanks, Gareth


From: "Gareth Vaughan" <gareth(at)specialisedstructures(dot)co(dot)nz>
To: "'Ricardo Martin Gomez'" <rimartingomez(at)hotmail(dot)com>, <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: RE: error restoring backup in version 4.4.1
Date: 2019-01-21 01:06:38
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Lists: pgadmin-support

Hi Ricardo

Thanks for looking at this so quickly!

I didn't run a second restore. I only used this to restore the backup to a
new db.

0) select Delete/Drop existing myDB from the browser panel

1) create a new db named myDB via the Create - Database dialogue accessible
from the browser panel

2) right click on the new myDB and select restore

3) navigate to the backup file, select the rolename and click restore

That process generates an error in 4.1 but works fine in 3.6

Gareth

From: Ricardo Martin Gomez [mailto:rimartingomez(at)hotmail(dot)com]
Sent: Monday, January 21, 2019 1:59 PM
To: pgadmin-support(at)lists(dot)postgresql(dot)org; Gareth Vaughan
<gareth(at)specialisedstructures(dot)co(dot)nz>
Subject: Re: error restoring backup in version 4.4.1

Hi Garreth,

When you run second restore.

Is the target database recreated recently?

Obtener Outlook para Android <https://aka.ms/ghei36>

_____

From: Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz
<mailto:gareth(at)specialisedstructures(dot)co(dot)nz> >
Sent: Sunday, January 20, 2019 5:57:22 PM
To: pgadmin-support(at)lists(dot)postgresql(dot)org
<mailto:pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: error restoring backup in version 4.4.1

Hi pgAdmin support

Thanks for the new version. I've tried updating but I've encountered a
small error.

I'm currently running postgres 10.4. I generate backups with something
like:

pg_dump.exe -Fc -U myRoleName -h localhost -p 5432 --dbname=myDb
--file=dbBackup.backup

To restore a backup to a new db in pgAdmin

1) create a new db via the Create - Database dialogue accessible from the
browser panel

2) right click on the newly created db and select restore

3) navigate to the backup file, select the rolename and click restore

in pgadmin 4.3.6

this process completes successfully

in pgadmin 4.4.1 this fails with

Failed (exit code 1)

here's the error from the detailed report:

pg_restore: creating SCHEMA "public"

pg_restore: [archiver (db)] Error while PROCESSING TOC:

pg_restore: [archiver (db)] Error from TOC entry 3; 2615 2200 SCHEMA public
myRoleName

pg_restore: [archiver (db)] could not execute query: ERROR: schema "public"
already exists

Command was: CREATE SCHEMA public;

Thanks, Gareth


From: Ricardo Martin Gomez <rimartingomez(at)hotmail(dot)com>
To: "pgadmin-support(at)lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>, Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz>
Subject: Re: error restoring backup in version 4.4.1
Date: 2019-01-21 01:15:41
Message-ID: SC1P15201MB2304C027DC7034A7FFD0B907A39F0@SC1P15201MB2304.LAMP152.PROD.OUTLOOK.COM
Views: Whole Thread | Raw Message | Download mbox | Resend email
Lists: pgadmin-support

OK,
In step (1), when you're creating the database.
Can you check that is selected template0 in both. (3.6 and 4.1)

Obtener Outlook para Android<https://aka.ms/ghei36>

________________________________
From: Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz>
Sent: Sunday, January 20, 2019 10:06:38 PM
To: 'Ricardo Martin Gomez'; pgadmin-support(at)lists(dot)postgresql(dot)org
Subject: RE: error restoring backup in version 4.4.1

Hi Ricardo

Thanks for looking at this so quickly!

I didn’t run a second restore. I only used this to restore the backup to a new db.

0) select Delete/Drop existing myDB from the browser panel
1) create a new db named myDB via the Create - Database dialogue accessible from the browser panel
2) right click on the new myDB and select restore
3) navigate to the backup file, select the rolename and click restore

That process generates an error in 4.1 but works fine in 3.6

Gareth

From: Ricardo Martin Gomez [mailto:rimartingomez(at)hotmail(dot)com]
Sent: Monday, January 21, 2019 1:59 PM
To: pgadmin-support(at)lists(dot)postgresql(dot)org; Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz>
Subject: Re: error restoring backup in version 4.4.1

Hi Garreth,
When you run second restore.
Is the target database recreated recently?
Obtener Outlook para Android<https://aka.ms/ghei36>

________________________________
From: Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz<mailto:gareth(at)specialisedstructures(dot)co(dot)nz>>
Sent: Sunday, January 20, 2019 5:57:22 PM
To: pgadmin-support(at)lists(dot)postgresql(dot)org<mailto:pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: error restoring backup in version 4.4.1

Hi pgAdmin support

Thanks for the new version. I've tried updating but I've encountered a small error.

I'm currently running postgres 10.4. I generate backups with something like:
pg_dump.exe -Fc -U myRoleName -h localhost -p 5432 --dbname=myDb --file=dbBackup.backup

To restore a backup to a new db in pgAdmin
1) create a new db via the Create - Database dialogue accessible from the browser panel
2) right click on the newly created db and select restore
3) navigate to the backup file, select the rolename and click restore

in pgadmin 4.3.6
this process completes successfully

in pgadmin 4.4.1 this fails with
Failed (exit code 1)
here's the error from the detailed report:

pg_restore: creating SCHEMA "public"
pg_restore: [archiver (db)] Error while PROCESSING TOC:
pg_restore: [archiver (db)] Error from TOC entry 3; 2615 2200 SCHEMA public myRoleName
pg_restore: [archiver (db)] could not execute query: ERROR: schema "public" already exists
Command was: CREATE SCHEMA public;

Thanks, Gareth


From: "Gareth Vaughan" <gareth(at)specialisedstructures(dot)co(dot)nz>
To: "'Ricardo Martin Gomez'" <rimartingomez(at)hotmail(dot)com>, <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: RE: error restoring backup in version 4.4.1
Date: 2019-01-21 01:37:22
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Lists: pgadmin-support

Initially, in both versions, the default template combo box has nothing
selected.

When Template0 has been selected I still get the error in 4.1, and version
3.6 still works.

From: Ricardo Martin Gomez [mailto:rimartingomez(at)hotmail(dot)com]
Sent: Monday, January 21, 2019 2:16 PM
To: pgadmin-support(at)lists(dot)postgresql(dot)org; Gareth Vaughan
<gareth(at)specialisedstructures(dot)co(dot)nz>
Subject: Re: error restoring backup in version 4.4.1

OK,

In step (1), when you're creating the database.

Can you check that is selected template0 in both. (3.6 and 4.1)

Obtener Outlook para Android <https://aka.ms/ghei36>

_____

From: Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz
<mailto:gareth(at)specialisedstructures(dot)co(dot)nz> >
Sent: Sunday, January 20, 2019 10:06:38 PM
To: 'Ricardo Martin Gomez'; pgadmin-support(at)lists(dot)postgresql(dot)org
<mailto:pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: RE: error restoring backup in version 4.4.1

Hi Ricardo

Thanks for looking at this so quickly!

I didn't run a second restore. I only used this to restore the backup to a
new db.

0) select Delete/Drop existing myDB from the browser panel

1) create a new db named myDB via the Create - Database dialogue accessible
from the browser panel

2) right click on the new myDB and select restore

3) navigate to the backup file, select the rolename and click restore

That process generates an error in 4.1 but works fine in 3.6

Gareth

From: Ricardo Martin Gomez [mailto:rimartingomez(at)hotmail(dot)com]
Sent: Monday, January 21, 2019 1:59 PM
To: pgadmin-support(at)lists(dot)postgresql(dot)org
<mailto:pgadmin-support(at)lists(dot)postgresql(dot)org> ; Gareth Vaughan
<gareth(at)specialisedstructures(dot)co(dot)nz
<mailto:gareth(at)specialisedstructures(dot)co(dot)nz> >
Subject: Re: error restoring backup in version 4.4.1

Hi Garreth,

When you run second restore.

Is the target database recreated recently?

Obtener Outlook para Android <https://aka.ms/ghei36>

_____

From: Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz
<mailto:gareth(at)specialisedstructures(dot)co(dot)nz> >
Sent: Sunday, January 20, 2019 5:57:22 PM
To: pgadmin-support(at)lists(dot)postgresql(dot)org
<mailto:pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: error restoring backup in version 4.4.1

Hi pgAdmin support

Thanks for the new version. I've tried updating but I've encountered a
small error.

I'm currently running postgres 10.4. I generate backups with something
like:

pg_dump.exe -Fc -U myRoleName -h localhost -p 5432 --dbname=myDb
--file=dbBackup.backup

To restore a backup to a new db in pgAdmin

1) create a new db via the Create - Database dialogue accessible from the
browser panel

2) right click on the newly created db and select restore

3) navigate to the backup file, select the rolename and click restore

in pgadmin 4.3.6

this process completes successfully

in pgadmin 4.4.1 this fails with

Failed (exit code 1)

here's the error from the detailed report:

pg_restore: creating SCHEMA "public"

pg_restore: [archiver (db)] Error while PROCESSING TOC:

pg_restore: [archiver (db)] Error from TOC entry 3; 2615 2200 SCHEMA public
myRoleName

pg_restore: [archiver (db)] could not execute query: ERROR: schema "public"
already exists

Command was: CREATE SCHEMA public;

Thanks, Gareth


From: Dave Page <dpage(at)pgadmin(dot)org>
To: Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz>
Cc: "pgadmin-support lists(dot)postgresql(dot)org" <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: Re: error restoring backup in version 4.4.1
Date: 2019-01-21 11:57:47
Message-ID: CA+OCxoydfX9uTe1CwZHei+3XEi6H1M-zkOsAetJ32AyvySw+jw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Lists: pgadmin-support

Hi

On Sun, Jan 20, 2019 at 8:57 PM Gareth Vaughan
<gareth(at)specialisedstructures(dot)co(dot)nz> wrote:
>
> Hi pgAdmin support
>
>
>
> Thanks for the new version. I've tried updating but I've encountered a small error.
>
>
>
> I'm currently running postgres 10.4. I generate backups with something like:
>
> pg_dump.exe -Fc -U myRoleName -h localhost -p 5432 --dbname=myDb --file=dbBackup.backup
>
>
>
>
>
> To restore a backup to a new db in pgAdmin
>
> 1) create a new db via the Create - Database dialogue accessible from the browser panel
>
> 2) right click on the newly created db and select restore
>
> 3) navigate to the backup file, select the rolename and click restore
>
>
>
> in pgadmin 4.3.6
>
> this process completes successfully
>
>
>
>
>
> in pgadmin 4.4.1 this fails with
>
> Failed (exit code 1)
>
> here's the error from the detailed report:
>
>
>
> pg_restore: creating SCHEMA "public"
>
> pg_restore: [archiver (db)] Error while PROCESSING TOC:
>
> pg_restore: [archiver (db)] Error from TOC entry 3; 2615 2200 SCHEMA public myRoleName
>
> pg_restore: [archiver (db)] could not execute query: ERROR: schema "public" already exists
>
> Command was: CREATE SCHEMA public;

At the top of the dialogue that shows the output, it should show the
command that was executed. Can you show us that for both cases please?
It should be something like:

/Library/PostgreSQL/10/bin/pg_dump --file "/Users/dpage/foo.sql"
--host "localhost" --port "5433" --username "postgres" --no-password
--verbose --format=c --blobs "postgres"

Thanks.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


From: "Gareth Vaughan" <gareth(at)specialisedstructures(dot)co(dot)nz>
To: "'Dave Page'" <dpage(at)pgadmin(dot)org>
Cc: "'pgadmin-support lists(dot)postgresql(dot)org'" <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: RE: error restoring backup in version 4.4.1
Date: 2019-01-21 22:18:33
Message-ID: [email protected]
Views: Whole Thread | Raw Message | Download mbox | Resend email
Lists: pgadmin-support

Hi

Command used in 3.6:
C:\Program Files (x86)\pgAdmin 4\v3\runtime\pg_restore.exe --host "localhost" --port "5432" --username "myUserName" --no-password --role " myRoleName " --dbname "myDB" --verbose "C:\\temp\\DB_ARC~1\\SSEB48~1.BAC

Command used in 4.1:
C:\Program Files (x86)\pgAdmin 4\v4\runtime\pg_restore.exe --host "localhost" --port "5432" --username " myUserName " --no-password --role " myRoleName " --dbname "myDB" --verbose "C:\\temp\\DB_ARC~1\\SSEB48~1.BAC"

Gareth

-----Original Message-----
From: Dave Page [mailto:dpage(at)pgadmin(dot)org]
Sent: Tuesday, January 22, 2019 12:58 AM
To: Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz>
Cc: pgadmin-support lists.postgresql.org <pgadmin-support(at)lists(dot)postgresql(dot)org>
Subject: Re: error restoring backup in version 4.4.1

Hi

On Sun, Jan 20, 2019 at 8:57 PM Gareth Vaughan <gareth(at)specialisedstructures(dot)co(dot)nz> wrote:
>
> Hi pgAdmin support
>
>
>
> Thanks for the new version. I've tried updating but I've encountered a small error.
>
>
>
> I'm currently running postgres 10.4. I generate backups with something like:
>
> pg_dump.exe -Fc -U myRoleName -h localhost -p 5432 --dbname=myDb
> --file=dbBackup.backup
>
>
>
>
>
> To restore a backup to a new db in pgAdmin
>
> 1) create a new db via the Create - Database dialogue accessible from
> the browser panel
>
> 2) right click on the newly created db and select restore
>
> 3) navigate to the backup file, select the rolename and click restore
>
>
>
> in pgadmin 4.3.6
>
> this process completes successfully
>
>
>
>
>
> in pgadmin 4.4.1 this fails with
>
> Failed (exit code 1)
>
> here's the error from the detailed report:
>
>
>
> pg_restore: creating SCHEMA "public"
>
> pg_restore: [archiver (db)] Error while PROCESSING TOC:
>
> pg_restore: [archiver (db)] Error from TOC entry 3; 2615 2200 SCHEMA
> public myRoleName
>
> pg_restore: [archiver (db)] could not execute query: ERROR: schema
> "public" already exists
>
> Command was: CREATE SCHEMA public;

At the top of the dialogue that shows the output, it should show the command that was executed. Can you show us that for both cases please?
It should be something like:

/Library/PostgreSQL/10/bin/pg_dump --file "/Users/dpage/foo.sql"
--host "localhost" --port "5433" --username "postgres" --no-password --verbose --format=c --blobs "postgres"

Thanks.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company